Skip to main content
Glama

A schedule's recent firings

list_schedule_runs
Read-only

Retrieve recent firings of one schedule, newest first, with start time, duration, success, and HTTP status to confirm whether the cron ran before troubleshooting the schedule, block, or version.

Instructions

Every recent firing of one schedule, newest first: when it started, how long it took, whether it succeeded, and what HTTP status the execution returned.

THIS is how you answer "did the cron actually run". list_schedules carries only the LAST outcome, and block execution logs exist only for blocks with logging switched on — so a healthy schedule with logging off leaves no trace anywhere else and looks exactly like one that never fired. Check here before touching the cron, the block or the version: the usual finding is that it ran fine every time and the real problem is elsewhere (start with canvasAheadOfPin on list_schedules).

httpStatus separates the failures a user can act on: 429 is a quota they can raise, 503 is the platform's problem, 500 is their code.

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": {
      "triggerId": "<triggerId>"
    },
    "name": "list_schedule_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many firings to return, newest first. Default 50.
triggerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, and the description adds real context: results are ordered newest-first, and a healthy schedule with logging off leaves no trace anywhere else — a non-obvious behavioral fact. It also interprets httpStatus codes (429 quota, 503 platform, 500 user code), which is genuine beyond-schema meaning; only pagination behavior past the limit is unaddressed.

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?

Front-loaded with what is returned, then when to use it, then how to read the status codes — a sensible funnel with no filler sentences. The three-paragraph layout is slightly heavy for a two-parameter list tool, but each block carries distinct information.

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?

With no output schema, the description correctly spells out the returned fields and ordering, and it explains failure interpretation. The main remaining hole is the required triggerId's meaning/provenance, which an agent must guess or discover elsewhere.

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 50%: limit is documented inline, but the required triggerId has no description anywhere. The phrase "one schedule" only loosely implies triggerId identifies the schedule; it never says where the id comes from (e.g. list_schedules) or what form it takes, so the description does not compensate for the coverage gap on the one mandatory parameter.

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?

States a concrete verb and resource (list recent firings of one schedule) and immediately enumerates the returned fields: start time, duration, success, HTTP status. It also explicitly separates itself from list_schedules, so an agent can pick it without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit triggering question ("did the cron actually run") plus a when-not: list_schedules carries only the LAST outcome and block execution logs only exist when logging is on. It also routes the agent onward ("start with canvasAheadOfPin on list_schedules") instead of leaving the next step implicit.

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