Skip to main content
Glama

List task runs

render_list_task_runs
Read-onlyIdempotent

List Render task runs filtered by owner, task slug, workflow, or root run ID; returns all accessible task runs if no filters are specified.

Instructions

List task runs. List task runs that match the provided filters. If no filters are provided, all task runs accessible by the authenticated user are returned. Calls GET /task-runs on the Render Public API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe maximum number of items to return. For details, see [Pagination](https://api-docs.render.com/reference/pagination).
cursorNoThe position in the result list to start from when fetching paginated results. For details, see [Pagination](https://api-docs.render.com/reference/pagination).
ownerIdNoThe ID of the workspaces to return resources for
taskSlugNoAn array of task slugs in the format workflow-slug/task-name. An optional version can be appended (workflow-slug/task-name:version). If no version is provided, the latest version is used.
workflowIdNoAn array of workflow IDs
rootTaskRunIdNoAn array of root task run IDs to filter on
workflowVersionIdNoAn array of workflow version IDs
Behavior3/5

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

Description adds HTTP method (GET) and default behavior (returns all accessible if no filters). Annotations already provide safety profile (readOnly, idempotent, non-destructive). No mention of pagination behavior, rate limits, or other traits beyond the schema.

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

Conciseness3/5

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

Three sentences; the first sentence repeats the title. Could be more concise by removing redundancy. Structure is acceptable but not optimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and description does not explain return values or structure. Despite parameter count (7) and optional filters, the description lacks completeness about what information is returned for each task run.

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 coverage is 100% with descriptions for all parameters, baseline 3. Description only generally mentions filtering without adding parameter-specific semantics beyond what schema provides.

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?

Description clearly states the tool lists task runs with optional filters and defaults to all accessible by user. However, it does not explicitly differentiate from siblings like render_get_task_run (single run) or render_get_task_runs_completed.

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?

No guidance on when to use this tool versus alternatives such as render_get_task_run for a single run or render_get_task_runs_completed. The description only states what the tool does without usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LuSrodri/render-useful-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server