Skip to main content
Glama

List workflow runs

writ_workflow_runs
Read-onlyIdempotent

Run history (status, timing, errors, venue) of one workflow or all of them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writ_workflow_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
deviceNo
statusNoFilter by status.
workflowNo
workflow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / device
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / workflow
      Added value: +{
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • removedInput schema / properties / device
      Removed value: -{
      -  "description": "A linked Writ desktop's agent_id (writ_devices) to act on. Omitted: the desktop this connection chose with writ_devices action='use', if any.",
      -  "type": "string"
      -}
    • changedInput schema / properties / status / description
      Previous value: -"pending|running|success|failed|cancelled|skipped"New value: +"Filter by status."
    • removedInput schema / properties / workflow
      Removed value: -{
      -  "type": "string"
      -}
  3. First observed

TDQS

B3.3/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. The description adds value by disclosing what each record contains (status, timing, errors, venue), which matters given there is no output schema. It says nothing about pagination, default ordering, or default result size for the undocumented limit parameter.

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

Conciseness5/5

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

A single sentence that front-loads the returned content and closes with the scoping rule. No filler, nothing repeated from the title.

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?

Covering the returned fields partially offsets the missing output schema, but a five-parameter tool at 20% schema coverage with an unresolved workflow/workflow_id ambiguity leaves the agent guessing. For a read-only listing tool this is adequate but not complete.

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 only 20% — just 'status' carries a description. The description does not distinguish workflow (name) from workflow_id (numeric id), does not explain limit semantics or defaults, and does not mention device. With four of five parameters undocumented anywhere, the description should have compensated and does not.

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 the resource precisely as 'Run history' and enumerates the content returned (status, timing, errors, venue), plus scope 'of one workflow or all of them'. An agent can tell it is a read of run records rather than a trigger, but it never names the sibling that starts a run (writ_run_workflow) or the data tool (writ_workflow_data), so differentiation is left to inference.

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?

The phrase 'of one workflow or all of them' implies the two usage modes (scoped vs global), which is modest guidance. There is no statement of when to prefer this over writ_run_workflow, writ_workflow_data, or writ_list_workflows, and no prerequisites or exclusions.

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.