Spaceship MCP

list_executions

Retrieve recent runs for an AI agent to review run history and check success status before starting a new run. Provides status and duration for each run.

Instructions

List recent runs for an agent with their status and duration.

Useful for reviewing run history or checking whether a previous run succeeded before starting a new one.

Args: agent_id: The agent's UUID. limit: Number of runs to return (default 10, max 50).

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": {
      "agent_id": "<agent_id>"
    },
    "name": "list_executions"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5May 5, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavior. The description implies read-only operation (listing runs) without stating non-destructiveness explicitly. It does not mention authentication needs, rate limits, or side effects, but the read-only nature is reasonably inferred.

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?

The description is concise with three short sections. It front-loads the purpose, adds usage context, and lists parameter details without superfluous text. However, it could be more structured (e.g., bullet points for Args) to improve readability.

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 that an output schema exists, the description does not need to explain return values. It covers purpose, usage, and parameters adequately for an agent to use the tool correctly. Minor gap: no mention of sorting or time range, but 'recent runs' implies recency.

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 0%, so the description compensates by explaining both parameters: 'agent_id: The agent's UUID' and 'limit: Number of runs to return (default 10, max 50).' This adds meaning beyond the schema, which only provides titles and types.

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 explicitly states 'List recent runs for an agent with their status and duration.' It uses a specific verb (list) and resource (runs), and differentiates from sibling list tools like list_agents and list_orchestrations by focusing on agent executions.

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 provides clear context: 'Useful for reviewing run history or checking whether a previous run succeeded before starting a new one.' It explains when to use the tool but does not explicitly mention when not to use it or suggest alternatives, though sibling names imply the distinctions.

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

Deploy Server