Skip to main content
Glama

List tasks

render_list_tasks
Read-onlyIdempotent

List workflow tasks using optional filters for owner, task slug, workflow ID, or version. Returns all accessible tasks if no filters are provided.

Instructions

List tasks. List workflow tasks that match the provided filters. If no filters are provided, all task definitions accessible by the authenticated user are returned. Calls GET /tasks 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
workflowVersionIdNoAn array of workflow version IDs
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the endpoint and default behavior but no additional behavioral traits.

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?

Three sentences, front-loaded with purpose, no extra fluff. Efficient and well-structured.

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?

Covers purpose and default behavior, but lacks description of the return format (e.g., paginated list) and does not mention that the response contains task definitions. Minor gap given the tool has no output schema.

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?

All parameters have descriptions in the input schema (100% coverage), so the description adds no extra parameter meaning beyond what's already documented.

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?

The description clearly states the verb 'List', the resource 'workflow tasks', and the scope (with filters or all). It distinguishes from siblings like render_list_task_runs (for task runs) and render_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 Guidelines4/5

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

The description explains that no filters return all task definitions, providing clear context. However, it does not explicitly mention when not to use this tool or suggest alternatives like render_get_task for a single task.

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