Skip to main content
Glama

tasks_list

Retrieve tasks with filters for assignee, project, parent task, or completion status.

Instructions

Get all tasks with optional filters.

Retrieves tasks using cursor-based pagination. Can filter by assignee, project, parent task, and completion status.

Workflow tips:

  • Use cursor for pagination through large result sets

  • Filter by assignee_id to see tasks for specific users

  • Filter by project_id to see project tasks

  • Filter by done status (0 = not done, 1 = done)

  • Filter by parent_task_id to see subtasks

Common use cases:

  • List all incomplete tasks: { "done": 0 }

  • Get tasks for a user: { "assignee_id": 123 }

  • Get project tasks: { "project_id": 456 }

  • Get subtasks: { "parent_task_id": 789 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoCursor for pagination
limitNoNumber of items to return (max 500)
assignee_idNoFilter by assignee ID
project_idNoFilter by project ID
parent_task_idNoFilter by parent task ID
doneNoFilter by done status (0 = not done, 1 = done)
Behavior5/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It explicitly mentions cursor-based pagination for large result sets, and all filtering behavior is clearly described. There is no contradictory information, and the description accurately reflects that the tool is a safe read operation.

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?

The description is concise yet comprehensive. It is structured with a clear main sentence, a pagination note, a bullet list of workflow tips, and then a list of common use cases with inline JSON examples. Every part serves a purpose, and there is no fluff.

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

Completeness5/5

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

Given that there are 6 optional parameters, no output schema, and no annotations, the description covers all necessary aspects: pagination (cursor/limit), all filter parameters with examples, and common query patterns. The agent has enough context to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description adds substantial value beyond the schema. It groups related parameters into workflows (e.g., pagination, filtering by assignee/project) and provides practical JSON examples showing common use cases, which helps an agent understand parameter combinations and usage patterns.

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 starts with 'Get all tasks with optional filters,' which clearly states the verb (get) and resource (tasks) with the key differentiator (optional filters). It explicitly mentions cursor-based pagination and filtering by assignee, project, parent task, and completion status, distinguishing it from sibling tools like projects_tasks_list (which is project-specific) and tasks_get (single task).

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 provides workflow tips and common use cases with concrete JSON examples, such as listing incomplete tasks or filtering by user. It implicitly guides the agent on when to use this tool (e.g., for listing tasks with filters) but does not explicitly state when not to use it or mention alternatives like projects_tasks_list. Still, the examples are highly instructive.

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/iamsamuelfraga/mcp-pipedrive'

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