Edworking MCP

List tasks

list_tasks

Read-onlyIdempotent

List accessible tasks, optionally in one project. Returns due dates, status, assignees, and source links. Keep ordering and filters unchanged across pages.

Input Schema

Name	Required	Description	Default
`after`	No	Pagination cursor from the previous nextCursor. Keep filters and ordering unchanged; omit for the first page.
`limit`	No	Maximum number of items to return, from 1 to 100. Defaults to 50.
`order`	No	Result ordering. Defaults to most recently updated first. Keep the same order while paging.	UPDATED_DESC
`query`	No	Search text. List tools filter names/titles; search queries indexed workspace content.
`dueAfter`	No	Inclusive earliest deadline, as ISO 8601 with timezone.
`priority`	No	Priority: 0 Low, 1 Normal, 2 High, 3 Urgent. For updates, null clears it.
`dueBefore`	No	Inclusive latest deadline, as ISO 8601 with timezone.
`projectId`	No	Existing accessible project ID returned by list_projects.
`assigneeId`	No	Filter tasks by this existing user ID.
`stateProjectId`	No	Task status ID from list_project_statuses for the destination project.

Output Schema

Name	Required	Description	Default
`items`	Yes	Accessible records on this page.
`nextCursor`	Yes	Pass as after for the next page; null when this page has no continuation cursor.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 14, 2026

addedInput schema / properties / assigneeId

Added value: +{
+  "description": "Filter tasks by this existing user ID.",
+  "maxLength": 100,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9_-]+$",
+  "type": "string"
+}

addedInput schema / properties / dueAfter

Added value: +{
+  "description": "Inclusive earliest deadline, as ISO 8601 with timezone.",
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+  "type": "string"
+}

addedInput schema / properties / dueBefore

Added value: +{
+  "description": "Inclusive latest deadline, as ISO 8601 with timezone.",
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+  "type": "string"
+}

addedInput schema / properties / priority

Added value: +{
+  "description": "Priority: 0 Low, 1 Normal, 2 High, 3 Urgent. For updates, null clears it.",
+  "maximum": 3,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Search text. List tools filter names/titles; search queries indexed workspace content.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / stateProjectId

Added value: +{
+  "description": "Task status ID from list_project_statuses for the destination project.",
+  "maxLength": 100,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9_-]+$",
+  "type": "string"
+}

First observedOct 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real value on top: the pagination stability requirement and a summary of the returned fields. It does not add auth/permission nuances, but with annotations this is a solid 4.

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 short sentences covering scope, return shape, and the pagination contract. Front-loaded with the primary action and free of filler.

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?

An output schema exists, so return values need not be enumerated in depth. With full parameter documentation and annotation-covered safety, the description is nearly complete for a read-only list tool; the only gap is the absence of explicit sibling routing.

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 every one of the 10 parameters is already documented in the schema, including the enum values for order and the list-vs-search note for query. The description adds no parameter-level detail beyond 'optionally in one project', so the baseline 3 applies.

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?

States a specific verb and resource ('List accessible tasks') plus an optional scope ('optionally in one project'), which is enough to distinguish it from get_task or edit_task_content. It doesn't name or differentiate itself from the other list_* siblings, keeping it just short of a 5.

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

Usage Guidelines3/5

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

The only guidance is the pagination constraint ('Keep ordering and filters unchanged across pages') and the implicit 'optionally in one project' scoping hint. There is no explicit routing such as when to use list_tasks versus search, or versus get_task for a single item; the list-vs-search distinction lives in the schema, not the description.

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

All Edworking MCP tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.