Skip to main content
Glama

Get agent run

get_agent_run
Read-only

Fetch one dispatched AI agent run in full: status, trigger context (e.g. the board ticket that spawned it), timings, the complete outcome summary (the run list clips it, this does not), goal status, the linked session id, and tool_iterations - how many tool calls the run's session actually made. Note that turns_used counts SESSIONS, not tool calls: a run that made thirty-six tool calls in one session still reports turns_used 1, so read tool_iterations for how much work happened. Set include_transcript to also inline the session transcript (what the agent actually said and did, with the assistant's prose in payload_text), readable for any run in the organisation. The transcript arrives one window at a time: by default the last transcript_limit events, and with since_sequence the events after that sequence - walk a long transcript by starting at since_sequence 0 and passing back next_since_sequence while transcript_has_more_after is true. Identify the run by run_id from list_agent_runs. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "run_id": "<run_id>"
    },
    "name": "get_agent_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run UUID.
since_sequenceNoReturn the transcript events AFTER this sequence number instead of the tail. Start at 0 to walk the transcript from the beginning, then pass back next_since_sequence from each response while transcript_has_more_after is true.
transcript_limitNoHow many transcript events one window carries (default 20). The window is the tail unless since_sequence is set.
include_transcriptNoAlso return a window of the linked session transcript (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, and the description adds substantial behavior beyond that: transcript is readable for any run in the organisation (authorization scope), the transcript arrives in windows rather than at once, and turns_used counts sessions not tool calls while tool_iterations reports actual tool-call volume — a non-obvious semantic trap it warns about explicitly. The 'Read-only' restatement is redundant with the annotation but harmless.

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

Conciseness4/5

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

Front-loaded with the return payload, then the turns_used caveat, then the transcript mechanics — a sensible ordering with no filler sentences. It is dense and long, and the trailing 'Read-only.' duplicates the readOnlyHint annotation, but nearly every clause carries information an agent needs.

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

Completeness5/5

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

With no output schema, the description carries the full burden of describing return values, and it does: it enumerates the fields returned, names payload_text as where assistant prose lives, and exposes the response-side pagination fields (next_since_sequence, transcript_has_more_after) needed to continue. For a four-parameter read tool this is complete.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline would be 3, but the description adds genuine meaning: it explains that tool_iterations (not turns_used) measures work done, and describes the since_sequence / next_since_sequence / transcript_has_more_after pagination loop as a coherent walk rather than isolated fields. It does not restate the transcript_limit maximum of 100 or the default of 20, leaving those to the schema.

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?

States a specific verb and resource ('Fetch one dispatched AI agent run in full') and then enumerates exactly what 'in full' means: status, trigger context, timings, complete outcome summary, goal status, session id, tool_iterations. It explicitly contrasts with the run list ('the run list clips it, this does not'), so an agent can distinguish it from list_agent_runs without opening the schema.

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?

Gives the prerequisite for invoking it ('Identify the run by run_id from list_agent_runs') and the alternative it supersedes (the clipped list view). It also scopes the optional path precisely: set include_transcript to inline the transcript, and walk a long transcript starting at since_sequence 0 while transcript_has_more_after is true.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.