globalize.now

List Workflow runs

list_workflow_runs

Read-only

A Workflow’s runs, newest first, each as get_workflow_run reports it. Cursor-paginated. A "completed" run has finished translating; it does not mean the translations were delivered. Its Outputs deliver after it completes: check each Output’s outcome (null until it has run, then delivered, failed or skipped) before telling the user the translations are in place. When referring to a project or language in your reply to the user, use its name and locale (e.g. "French (fr-FR)") — ids (UUIDs) are for tool calls only, never show them to the user.

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": {
      "workflowId": "<workflowId>"
    },
    "name": "list_workflow_runs"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size (default 50)
`cursor`	No	Pagination cursor from a previous call
`workflowId`	Yes	Workflow id, from list_workflows or set_up_workflow

Output Schema

Name	Required	Description	Default
`data`	Yes
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), yet the description adds real value: cursor pagination, newest-first ordering, the caveat that "completed" means translation finished rather than delivered, and that each Output's outcome must be checked (null, delivered, failed, skipped) before reporting success. It omits any permission or rate-limit notes, so not a 5.

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?

The core purpose and pagination are front-loaded in the first two short sentences, and the run-status caveat is genuinely relevant. The trailing instruction about showing names/locales instead of UUIDs is general reply boilerplate rather than tool-specific behavior, slightly diluting focus.

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 an output schema present, the description needn't explain return values, and it correctly spends its words on the non-obvious semantics (run status vs. Output outcome) that the schema cannot convey. Complete enough to call and interpret correctly, though it never states the relationship to get_workflow_run for drill-down.

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%, so limit, cursor, and workflowId are already documented in the schema. The description only echoes pagination ("Cursor-paginated") without adding format or constraint detail beyond what the schema provides, 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 opening sentence names the resource (a Workflow's runs) and states ordering (newest first) plus item shape by reference to get_workflow_run. It implicitly distinguishes the collection from the singular get_workflow_run, but never explicitly contrasts with that sibling or with list_workflows.

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: call this to enumerate runs for a given workflowId. The description gives no explicit when-to-use / when-not-to-use guidance or named alternative (e.g. use get_workflow_run for a single run's detail), leaving the agent to infer the choice.

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

All globalize.now tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.