DocsTools Timeline

Tools: Timeline

The Timeline tool your agent sees through Elixir MCP: what each one answers, what it takes, and which capability it needs.

‹ All tools

Timeline

1 of the 55 tools in the registry. Generated from what tools/list returns, so this is exactly what your agent sees.

Timeline elixir_timeline

Your timeline: what happened to the players and clans you track since your read pointer, as ITEMS in order plus one summary ENTRY per subject. A person's subjects are the players they track and the clans they added; an agent's is the clan it represents, whose members appear on the clan's timeline. Items are named moments with an instant: battle sessions (a 30-minute gap breaks a session; single battles never appear), badges by name, arena and ranked moves, new bests, cards unlocked, joins, departures, role changes, the boat crossing the line, a week resolving, quiet rungs crossed, returns, and your account events. Each entry opens with a sentence a person can read, then always-present sections. Facts, never advice; nothing announces the time (game_clock does). Omit from to read from your pointer (none: last 24 hours; capped at 30 days). mark_read moves the pointer to the window end; a dry run passes false. Needs only cr:read.

Read-only · requires cr:read

ArgumentTypeRequiredNotes
from string no Start of the window, inclusive: an ISO instant, or YYYY-MM-DD resolving to local midnight in your timezone.
to string no End of the window, exclusive: an ISO instant as given; YYYY-MM-DD covers that WHOLE local day. Omit for up to now.
days integer no Last N days, ending now: sugar for from. Or use from/to.
weeks integer no Last N weeks, ending now: sugar for from. Or use from/to.
timezone string no IANA zone (e.g. Europe/Paris) for this call's date-only bounds and local labels. Default: the account's timezone. Agents serving people in several zones pass the asker's.
mark_read boolean no Move your read pointer to this window's end. A dry run, or a second consumer on the same account, passes false and keeps its own from.
sections array no Keep only items and entry sections in these sections; the summary, subject, window and player notables always stay. Player sections: battles, trophies, arena, ranked, collection, badges, clan, war, presence. Clan sections: activity, roster, war, presence, standouts, donations. Plus account.
kinds array no Keep only timeline items of these kinds (entries are untouched): battle_session, session_standout, badge_earned, legendary_badge_earned, arena_changed, ranked_promotion, best_trophies_band, collection_level_step, career_wins_step, card_unlocked, clan_joined, clan_left, member_joined, member_left, member_role_changed, bracket_observed, race_finished, week_resolved, quiet_crossed, returned, or an account_* kind. A consumer that wakes on a few kinds reads only those.
verbosity string no compact: the timeline items and each entry's summary, subject, window and player notables; every entry section, including clan standouts, is dropped. (full · compact)

What comes back (declared outputSchema; fields marked required are always present):

FieldTypeRequiredNotes
applied object yes
window object yes
read_to string | null yes
timeline array yes
timeline_more integer no
entries array yes
quiet array yes
subjects integer no
next_cursor string yes ISO 8601 UTC instant.
has_more boolean yes
notes array yes One-sentence caveats to repeat when quoting the numbers.
docs string yes page or page#section for elixir_docs / elixir://docs.
meta object yes The envelope (docs: responses).