Skip to main content
Glama

List recent executions

list_recent_executions
Read-only

List recent platform executions (deployments, write operations) for the current cluster, or across the whole organisation when the conversation is not opened on a cluster (pass cluster_id or cluster_name to narrow). Returns: id, name, status, error_excerpt, step_summary (succeeded/failed counts), and timestamps. Use this to investigate what changed recently or which deployments failed. Filter by status (e.g., 'failed', 'critical', 'running') for focused queries.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "list_recent_executions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of executions to return. Default 10, max 50.
statusNoOptional list of execution statuses to filter by. Use ['failed', 'critical'] to find recent failures.
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
include_internal_executionsNoIf true, also list the platform's internal maintenance executions that the default listing hides: GitOps reconcile ticks (name gitops_reconcile_attempt, 'GitOps reconcile') that landed no commit. A reconcile that pushed a 'Sync cluster state from Ankra' commit, possibly re-encrypting sealed files, is listed by default and names the commit and files in its detail's git_push. Default false; the same flag as the REST executions list's include_internal_executions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only cover readOnlyHint=true, so the description adds genuine value by enumerating the returned fields (id, name, status, error_excerpt, step_summary, timestamps) in the absence of an output schema, and by framing the tool as an investigative read. It omits ordering guarantees and pagination/truncation behavior, which limits it to a 4.

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

Conciseness3/5

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

The first sentence front-loads the scope and the return-shape sentence is compact and useful. But the parenthetical about organisation-wide listing and cluster_name is both verbose and wrong, and it sits at the most prominent position in the definition, hurting rather than helping.

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

Completeness3/5

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

For a four-parameter read-only list tool the definition covers purpose, return shape, and the status filter well enough to call it. The unresolved conflict between the described org-wide mode and the required cluster_id parameter means an agent cannot confidently determine what to pass when no cluster context exists.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would be 3, but the description actively misleads on parameters: it promises an organisation-wide listing when the schema marks cluster_id as required, and it tells the agent to "pass cluster_id or cluster_name" although no cluster_name parameter exists. These inaccuracies reduce meaning rather than adding it.

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

Purpose4/5

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

States a specific verb and resource ("List recent platform executions") plus what counts as an execution (deployments, write operations), which is more than a restatement of the name. It does not name the siblings that overlap most (get_execution_details, get_execution_trends, wait_for_execution, list_agent_runs), so the agent must infer differentiation itself.

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

Usage Guidelines3/5

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

"Use this to investigate what changed recently or which deployments failed" gives a real investigative context, and the status-filter hint is concretely actionable. However, no alternative is named for the adjacent jobs (drilling into one execution with get_execution_details, or spotting long-term patterns with get_execution_trends), so routing between siblings remains implied rather than stated.

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.