Skip to main content
Glama

list_tasks

Retrieve tasks from a plan or bucket with advanced filters like priority, due dates, assignees, completion status, and keyword search.

Instructions

List tasks in a plan or bucket with advanced filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of tasks to skip (for pagination, use with limit)
limitNoMaximum number of tasks to return (pagination)
fieldsNoComma-separated field names to return (e.g., 'id,title,bucketId,percentComplete') - reduces token usage
planIdNoPlan ID (optional - if not provided, lists tasks assigned to you)
searchNoSearch tasks by keyword using fuzzy matching. Matches against title, and description if includeDetails is true.
bucketIdNoBucket ID (optional - filters by bucket within the plan)
dueAfterNoDue date after this date (ISO 8601: '2026-03-27' or relative: 'today', 'tomorrow', 'next-week')
priorityNoFilter by priority, supports multiple values (OR logic). e.g. [1,3] for urgent+important. Values: 1=urgent, 3=important, 5=medium, 9=low
dueBeforeNoDue date before this date (ISO 8601: '2026-03-27' or relative: 'today', 'tomorrow', 'next-week')
isArchivedNoFilter by archived status (true/false/undefined for both)
assignedToMeNoFilter by tasks assigned to current user (only works with planId)
createdAfterNoCreated after this date (ISO 8601 or relative: 'today', 'this-week', 'last-week')
createdBeforeNoCreated before this date (ISO 8601 or relative: 'today', 'this-week', 'last-week')
completedAfterNoCompleted after this date (ISO 8601 or relative)
includeDetailsNoInclude task details (description, checklist, references) via $expand=details
completedBeforeNoCompleted before this date (ISO 8601 or relative)
percentCompleteNoFilter by percent complete. Supports comparison operators: '>50', '>=50', '<100', '<=100', or exact value '50'. Use 0 for not started, 100 for completed
searchThresholdNoFuzzy search sensitivity: 0.0 = exact match only, 1.0 = match anything. Default is 0.4.
appliedCategoriesNoFilter tasks by categories, comma-separated (e.g., 'category1' or 'category1,category3'). Returns tasks that have ALL specified categories set to true.
assignedToUserIdsNoFilter tasks assigned to any of the specified user IDs (OR logic). e.g. ['user-id-1', 'user-id-2']
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits like pagination limits, permission requirements, or whether only accessible tasks are returned. The description is insufficient for a complex tool with many parameters.

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 description is a single, front-loaded sentence with no wasted words. It is concise, though it could include more useful information without sacrificing brevity.

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?

Given 20 parameters, no output schema, and no annotations, the description is too brief. It does not explain the return format or how to leverage advanced filtering, making it incomplete for effective use.

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 the schema already documents all parameters effectively. The description adds no additional meaning beyond the schema, resulting in a baseline score of 3.

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 tool lists tasks in a plan or bucket with advanced filtering. It uses specific verb and resource, and distinguishes from siblings like get_task (single task) and list_buckets (different resource).

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 implies when to use it (when listing tasks in a plan/bucket with filtering) but does not explicitly state when not to use it or provide alternatives. Context is clear but lacks exclusions.

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/Plong-Wasin/planner-mcp'

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