delega-mcp

list_tasks

Retrieve compact, paginated task summaries with filters, total counts, and next_offset for full discovery. Workers see involved tasks; coordinators/admins see all account tasks.

Instructions

List compact, paginated task summaries with total/has_more/next_offset. Default 25 tasks and 6000 characters; follow next_offset with identical filters for complete discovery. A page is not the whole queue. Workers see involved tasks; coordinators/admins see all account tasks. Act only on your assignments or unowned tasks you claim; coordinate on others through comments. Use get_task for details and get_task_context for selected current state, not a full backlog dump.

Input Schema

TableJSON Schema

Name	Required	Description
`due`	No	Filter by due date category
`sort`	No
`label`	No	Filter by label name
`limit`	No	Maximum tasks to fetch (default 25); response budget can show fewer
`state`	No
`offset`	No	Use next_offset from the previous page (default 0)
`search`	No	Search task title and description
`claimed`	No	Filter by claim status (true = currently claimed tasks)
`completed`	No	Filter by completion status
`max_chars`	No	Maximum response characters (default 6000); omitted data remains explicitly retrievable.
`project_id`	No	Filter by project ID
`assigned_to`	No	Agent ID/external ID, or none for unassigned tasks

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv1.19.0Sep 11, 2026

addedInput schema / properties / assigned_to

Added value: +{
+  "description": "Agent ID/external ID, or none for unassigned tasks",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum tasks to fetch (default 25); response budget can show fewer",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / max_chars

Added value: +{
+  "description": "Maximum response characters (default 6000); omitted data remains explicitly retrievable.",
+  "maximum": 16000,
+  "minimum": 1000,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Use next_offset from the previous page (default 0)",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

removedInput schema / properties / project_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]

addedInput schema / properties / project_id / type
```
Added value: +[
+  "string",
+  "number"
+]
```

addedInput schema / properties / search

Added value: +{
+  "description": "Search task title and description",
+  "type": "string"
+}

addedInput schema / properties / sort

Added value: +{
+  "enum": [
+    "priority",
+    "updated",
+    "due",
+    "completed"
+  ],
+  "type": "string"
+}

addedInput schema / properties / state

Added value: +{
+  "enum": [
+    "working",
+    "waiting_input",
+    "errored"
+  ],
+  "type": "string"
+}

Changed5 schema fields changedv1.9.0Jun 10, 2026

addedInput schema / properties / claimed

Added value: +{
+  "description": "Filter by claim status (true = currently claimed tasks)",
+  "type": "boolean"
+}

addedInput schema / properties / project_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]

removedInput schema / properties / project_id / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / project_id / minimum
```
Removed value: --9007199254740991
```
removedInput schema / properties / project_id / type
```
Removed value: -"integer"
```

Changed3 schema fields changedv1.2.1May 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / project_id / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / project_id / minimum
```
Added value: +-9007199254740991
```
First observedv1.0.3Mar 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations provided, so the description carries the burden and does well: discloses pagination behavior, default limits (25 tasks, 6000 chars), the 'not the whole queue' caveat, role-based visibility (workers vs admins), and mutation etiquette (act/claim/comment). It does not explicitly state side effects beyond comments, but this is a read-list tool.

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?

Front-loads the core purpose and pagination guidance, then role and action guidance. Dense but every sentence is functional; slightly verbose in the multi-clause policy sentence, but not wasteful.

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?

For a 12-param list tool with no output schema, the description covers pagination, visibility, role behavior, and sibling alternatives. It stops short of documenting specific filters (delegated to schema), which is acceptable given 83% coverage. No output schema means more detail on returned fields could help, but the pagination hint covers the main risk.

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 83%, so the schema documents most parameters (limit, offset, max_chars, due, etc.). The description reinforces pagination semantics (next_offset with identical filters, page size defaults) but adds little parameter-specific syntax beyond that. Baseline 3 applies.

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?

States a specific verb (list) and resource (task summaries), specifies the compact paginated form, and distinguishes itself from siblings by naming get_task for details and get_task_context for selected state. An agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit alternatives: get_task for details, get_task_context for selected state. Also gives follow-up pagination guidance ('follow next_offset with identical filters') and scopes behavior by role (workers vs coordinators/admins) with action guidance on whose tasks to act on.

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

list_tasks

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools