Skip to main content
Glama

list_agent_runs

Obtain resumable session IDs for all agents in a run, enabling independent conversation resumption of each agent.

Instructions

List every agent that ran within one run and the real, resumable session id each was given.

This is how an orchestrating agent discovers the independently-resumable session_id of every agent — the run's main/supervisor agent and any subagents it dispatched — that participated in a specific run_id (obtained from list_runs, get_run, or a RunOutcome). Each captured session id can then be used to resume that one agent's conversation on its own, independently of the others, later.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesIdentifier for one invocation of a pooled agent — a lowercase-hex UUID minted per run, distinct from the session UUID: a run is a single dispatch, a session is the resumable conversation a run continues.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It explains the output (real, resumable session IDs) and implies read-only behavior, but does not explicitly state safety, side effects, or permissions. Adequate but could be more explicit.

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?

Description is clear and front-loaded with the core purpose. Second paragraph adds valuable usage context, though slightly wordy. No wasted sentences.

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?

Given the simple parameter set and existence of output schema, the description is complete. It explains the tool's role in the workflow and references sibling tools, providing sufficient context for an agent to use it correctly.

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 100% with detailed description of run_id. The description adds context by explaining why run_id is needed and how to obtain it, going beyond the schema's format specification.

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 verb 'list' and the specific resource: every agent that ran within one run and their session ID. It distinguishes from sibling tools like list_runs by explaining that it discovers resumable session IDs from a given run_id.

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

Usage Guidelines4/5

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

The description explicitly says when to use this tool: after obtaining a run_id from list_runs, get_run, or RunOutcome, to get session IDs for resuming agents. It does not mention when not to use it, but the context is clear.

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/Magic-Man-us/claude-sdk-agent-fleet'

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