Skip to main content
Glama

abx_get_action_runs_by_action_id

Read-onlyIdempotent

Fetch all execution runs for a given action ID, with page and size parameters, to review action history and troubleshoot automation behavior.

Instructions

Fetch all action runs of an action Retrieves all action runs of an action GET /abx/api/resources/actions/{id}/action-runs

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": {
      "id": "<id>"
    },
    "name": "abx_get_action_runs_by_action_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID of the action (path)
pageNoPage to fetch (starting from 0)
sizeNoAmount of entities per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that — no pagination behavior, ordering, or response characteristics — and merely restates 'fetch all' twice.

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

Conciseness2/5

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

Three lines say the same thing: 'Fetch all action runs of an action', 'Retrieves all action runs of an action', and the GET path. The duplication is waste, not reinforcement, and nothing is front-loaded beyond the first line.

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 simple read-only list endpoint with full schema coverage and rich annotations, the description is adequate but thin — it omits any hint of return shape or list ordering, which would help since there is no output schema.

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

Parameters3/5

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

Schema description coverage is 100%, with id, page and size each documented inline, so the baseline is 3. The description only echoes the path parameter '{id}' and adds no semantics for pagination parameters beyond the schema.

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 ('Fetch all action runs of an action') and the REST path confirms the scope is limited to a single action id. It is distinguishable from abx_get_action_run_by_id (singular) by wording, though it does not explicitly name siblings like abx_get_all_action_run_projections.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives such as abx_get_all_action_run_projections or abx_get_action_run_by_id, and no mention of prerequisites. Usage is only weakly implied by the 'of an action' phrasing.

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

Deploy Server

Other Tools