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 47 tools in the registry. Generated from what tools/list returns, so this is exactly what your agent sees.

Timeline elixir_timeline

Your newest-first timeline for tracked players and clans: one item per story (time-free text, subjects, visibility, publishable) plus subject summaries. basis occurred reads what happened in a window; a poller (reader, pointer) reads what the record learned, and omitting from starts at the pointer (default 24 hours, cap 30 days). evidence_item_id reads one item's ordered canonical games, version-pinned; evidence reads keep every pointer. Facts, never advice; game_clock supplies timing.

Read-only · requires cr:read

ArgumentTypeRequiredNotes
from string no Window start, EXCLUSIVE: items the record observed after this instant (ISO, or YYYY-MM-DD in your timezone). Omit to read since the read pointer. With basis occurred, when items happened instead.
to string no Window end, INCLUSIVE: items observed up to and including this instant, compared at the millisecond the tool serves; a date-only to covers that whole day. Omit for now. With basis occurred, when items happened instead.
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.
season string | integer no Bound the window to one season: 'current' (to date), 'previous', the month the API names it by (2026-08), or the river race season number (135). from/to/days/weeks given win over it.
evidence_item_id string no Read canonical game evidence for one visible item in this window. Always keeps the read pointer; use the original from/to. expected_evidence_version is required after the first page. Constituent games page independently of the newsfeed.
evidence_offset integer no
evidence_limit integer no
expected_evidence_version string no Pin the item's evidence version across pages; changed evidence asks you to reread the item.
mark_read boolean no Move the read pointer (the reader's, or the account's) to this window's end; false is a dry run that keeps it. Defaults to true on an observed read and false on an occurred one, which never moves a pointer.
basis string no What the window bounds (11.8.0). occurred: items that HAPPENED in (from, to], by sort_at, for 'what happened on Saturday'; never moves a pointer. observed: items the record LEARNED in (from, to], for polling, so nothing learned late is skipped; an item that happened before from carries late: true. Default: observed for a poller (a reader, the stored pointer, or mark_read true), otherwise occurred. (occurred · observed)
reader string no A name for THIS consumer's read pointer (3.18.0): omit from to read since it, mark_read moves it and read_to reports it; other readers on the same account keep theirs, and the account's unnamed pointer is untouched. meta.timeline_pending counts against the oldest named pointer. Lowercase letters, digits and hyphens, up to 32.
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, and attested (9.2.0: what a person did in a clan through a family app, or a family app's game produced for a player, said as theirs).
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, card_form_unlocked, clan_joined, clan_left, member_joined, member_left, member_role_changed, bracket_observed, race_finished, week_resolved, quiet_crossed, returned, the attested facts (departure_classified, role_change_made, award_granted, award_standing, member_away, clan_message, personal_record; each shown only to the reader its type allows), or an account_* kind. A consumer that wakes on a few kinds reads only those.
player_tag string no Keep only items about this player (7.1.5): their own moments and sessions and, on a clan's timeline, their member moments and sessions. Applied before the item cap; entries are untouched, and a member read never moves the read pointer.
skip_empty boolean no For polling (11.7.0): true answers a window with no item your kinds would keep without building it: timeline, entries and quiet empty, entries_skipped true; the pointer, next_cursor and meta move as on any read. Read without it when you want the entries.
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
evidence object no
applied object yes
window object yes
read_to string | null yes
timeline array yes
timeline_more integer no
timeline_more_to string | null no When has_more: the instant the page was cut at. Read the older, counted items by passing the same from with this as to and mark_read false (9.1.0). Null when nothing was cut.
entries array yes
entries_skipped boolean no 11.7.0: true when skip_empty found no item for this read and the entries and quiet were not built; false on every other read.
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).
Something wrong on this page?

Help for Tools: Timeline

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

Read more

The page you are on rides along. Every item is answered, and the answer comes to your email and your timeline.