Skip to main content
Glama

list_trigger_executions

Read-onlyIdempotent

Retrieve execution records for a specific trigger to inspect recent runs and delivery outcomes, using limit and offset pagination.

Instructions

List execution records for a trigger to inspect recent runs and delivery results.

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": {
      "trigger_id": "<trigger_id>"
    },
    "name": "list_trigger_executions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results; defaults to 20, maximum 100
offsetNoPagination offset
trigger_idYesTrigger UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.4
    • changedInput schema / properties / limit / description
      Previous value: -"Limite de resultados (default: 20, max: 100)"New value: +"Maximum results; defaults to 20, maximum 100"
    • changedInput schema / properties / offset / description
      Previous value: -"Offset para paginação"New value: +"Pagination offset"
    • changedInput schema / properties / trigger_id / description
      Previous value: -"UUID do trigger"New value: +"Trigger UUID"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description adds that records include delivery results, which is mild context beyond annotations, but says nothing about ordering, retention window, or pagination behavior.

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?

A single front-loaded sentence with the resource and the motivating use case; no filler or restatement of the title. It is efficient, though quite thin for a listing tool with pagination.

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 listing tool with rich annotations and a fully documented schema, the essentials are present. The remaining gap is return-shape context: with no output schema, the description only vaguely says 'execution records' and 'delivery results' without indicating fields, ordering, or whether pagination applies beyond the offset parameter.

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 limit, offset and trigger_id all documented in-schema including defaults and bounds. The description contributes no additional meaning about these parameters, so the baseline 3 applies.

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?

The description states a specific verb and resource ('List execution records for a trigger') plus the intent ('inspect recent runs and delivery results'), which is clearly distinct from mutation siblings like create_trigger or toggle_trigger. It does not explicitly differentiate itself from the singular get_trigger_execution or the generic list_executions, so an agent must infer the boundary.

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?

Usage is implied by 'to inspect recent runs and delivery results', which signals a read/inspection scenario. However, there is no explicit when-to-use versus when-not guidance and no named alternative for retrieving a single execution record, leaving the choice between this and get_trigger_execution to inference.

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