Skip to main content
Glama

List Tasks

list_tasks

Retrieve tasks filtered by entity, assignee, status, priority, due date, or tags. Check the render field for tiered guidance on composing your reply.

Instructions

List tasks with rich filtering. Omitting scope returns both org tasks and the caller's personal tasks. Filter by entity_type + entity_id to see tasks linked to a specific customer, transaction, etc. Use assigned_to='@claude' to surface the AI work queue. Response includes a render field with tiered rendering guidance - check it before composing your reply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoConvenience filter for a single tag. Use `tags` for multiple.
tagsNoFilter to items carrying these tags. Combined per `tag_match` (default 'all': the item must carry every listed tag).
limitNoMax results. Defaults to 50.
scopeNoFilter by scope. Omit to return both org and caller's personal tasks.
statusNoFilter by status.
priorityNoFilter by priority.
timezoneNoIANA timezone string (e.g. 'America/New_York'). When provided, 'today' is computed in the user's local timezone rather than UTC. Affects overdue_only filter.
due_afterNoReturn tasks due on or after this date (YYYY-MM-DD).
entity_idNoFilter to tasks linked to this entity ID. Requires entity_type.
tag_matchNoHow to combine `tags`: 'all' (item has every tag, default) or 'any' (item has at least one of them).
created_byNoFilter by creator user ID.
due_beforeNoReturn tasks due on or before this date (YYYY-MM-DD).
assigned_toNoFilter by assignee. Use a user ID, '@claude', '@gpt', or 'unassigned'.
entity_typeNoFilter to tasks linked to this entity type.
overdue_onlyNoIf true, only return tasks past their due date that are not done.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the response includes a render field with tiered guidance, but does not mention pagination, performance, or read-only nature (though implied). Adequate but could be richer.

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 with five sentences, each serving a purpose. It front-loads the core purpose and adds specific guidance without redundancy.

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?

Given no output schema and 15 parameters, the description covers default behavior, important filters, and response features. It lacks details on ordering or full response structure, but is largely sufficient for a list tool.

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

Parameters4/5

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

Schema coverage is 100% with parameter descriptions. The description adds value by providing usage patterns (e.g., assigned_to='@claude') beyond the schema, helping the agent select parameters effectively.

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 clearly states 'List tasks with rich filtering' and provides specific use cases (scope, entity_type+entity_id, assigned_to). However, it does not differentiate from the sibling tool 'list_entity_tasks', which may overlap in functionality.

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 gives explicit guidance for common scenarios (omitting scope, filtering by entity, using '@claude' for AI queue). It does not mention when NOT to use this tool or compare with alternatives, but the provided context is actionable.

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/OurThinkTank/founders-os'

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