Skip to main content
Glama

get_session_timeline

Access a session's event timeline in chronological order. Supports getting the last events with 'tail' and paginating with 'offset'.

Instructions

Get a chronological timeline of events in a session. Supports session id prefix match. Use 'tail' to get only the last N events (great for checking how a session ended). Use 'offset' to paginate through long sessions. NOT for searching — if you're looking for something specific in a session, use search_in_context instead of paginating this tool in a loop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
limitNoMax events to return (default 100)
offsetNoSkip first N events (for pagination)
tailNoReturn only the last N events of the session
include_thinkingNo
event_typeNoFilter to a single event type
summary_onlyNoReturn only event_type, timestamp, tool_name, file_path — no content. Great for scanning long sessions.
max_charsNoMax total output characters
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries full burden. It discloses support for session ID prefix match, tail, and offset for pagination. However, it does not explicitly state that the operation is read-only or describe ordering details beyond 'chronological', which are minor omissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with five sentences. The first sentence front-loads the main purpose, followed by key usage patterns and a clear warning. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters and no output schema, the description covers essential usage patterns (prefix match, tail, offset, not for searching) but could elaborate on return format or ordering beyond 'chronological'. However, schema covers parameter details, making it fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 75% schema coverage, the description adds significant meaning beyond the schema. It explains the purpose of tail and offset, and notes that session_id supports prefix matching, which is not in the schema. It also warns against using the tool for searching.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves a chronological timeline of events in a session. It distinguishes itself from sibling tools like search_in_context by explicitly stating it is not for searching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool (chronological timeline) and when not (searching). It also explains specific use cases for tail and offset, and names the alternative tool for searching.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Wynelson94/longhand'

If you have feedback or need assistance with the MCP directory API, please join our Discord server