Skip to main content
Glama

list_workflow_runs

Read-only

Recent workflow activity: each message a workflow sent (or drafted, or failed to send), with the client and the exact text. Optionally filter to one workflow.

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": "list_workflow_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
workflowIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real value by describing what each record contains (sent/drafted/failed message, client, exact text). It does not mention ordering, pagination behavior, or truncation of long message text, which are the remaining behavioral gaps.

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?

Two sentences, front-loaded with what the tool returns before the optional filter, and the parenthetical about sent/drafted/failed adds precision without waste. Nothing is redundant with the name or annotations.

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?

With no output schema, the description usefully sketches the shape of returned records, which an agent otherwise could not know. However, for a paged list tool it omits result-count/ordering behavior and the meaning of the limit parameter, leaving an agent unable to size requests confidently.

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 description coverage is 0%, so the description must carry both parameters. It only hints at workflowId ('filter to one workflow') without stating that the value is an ID, and never explains 'limit' at all – its default of 30, maximum of 200, or how ordering interacts with recency are undocumented anywhere.

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 defines the resource concretely: workflow 'runs' are clarified as each message a workflow sent, drafted, or failed to send, including client and exact text. This goes beyond the bare name and lets an agent distinguish run/activity data from approval or template listings. It stops short of explicitly contrasting with siblings such as list_ai_run_history or list_workflow_approvals.

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?

The only usage statement is 'Optionally filter to one workflow,' which explains the workflowId parameter but gives no guidance on when this tool should be chosen over the many other list_* tools. 'Recent' implies a time-bounded default, but no conditions, exclusions, or alternatives are named.

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.