xTiles

xtiles_list_tasks

Read-onlyIdempotent

List tasks with optional filters. Provide projectId to list project tasks, or omit for your personal tasks.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number, 1-based — the first page is 1. Defaults to 1.
`sort`	No	Sort field. Allowed values: due_date, created_at, priority. Defaults to "due_date".
`order`	No	Sort order (default: "asc")
`per_page`	No	Page size, 1–100. Defaults to 20.
`priority`	No	Task priority. Allowed values: LOW, MEDIUM, HIGH.
`completed`	No	Filter by completed status. Defaults to false if omitted (only open tasks are returned).
`projectId`	No	Project ID. Omit to list your own tasks (/my/tasks).
`due_date_after`	No	Inclusive lower bound — tasks due on or after this date. A calendar day (yyyy-MM-dd) is resolved to the start of that day in the user's timezone, so the named day IS included. Combine with due_date_before to form a half-open range [after, before) — same convention as Google Calendar timeMin/timeMax.
`due_date_before`	No	Exclusive upper bound — tasks due strictly before this date; the named day is NOT included (a calendar day yyyy-MM-dd is resolved to the start of that day in the user's timezone). To cover a whole single day D, pass the NEXT day as the bound: due_date_after=D and due_date_before=D+1 (e.g. tasks due "today" = after today AND before tomorrow). Passing the same date to both bounds returns nothing (empty range).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, so safety is covered. The description adds the crucial scope behavior that projectId toggles between project tasks and personal tasks — a behavioral default beyond what annotations provide. It doesn't mention pagination defaults or the fact that only open tasks are returned by default, though the schema covers the latter.

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?

Two concise sentences, front-loaded with the core action and directly followed by the critical scoping rule. No wasted words.

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 9 optional parameters, no required ones, and a complete schema, the description covers the essential scope decision and filter hint. With an output schema present, return values need not be described. The only minor gap is not mentioning pagination or default sort, but these are well-covered in the schema.

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%, so parameters are fully documented. The description adds the explicit projectId semantics (project vs personal) which, although also in the schema, reinforces the branching logic. Filters are implied but not enumerated, which is acceptable given schema completeness.

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+resource ('List tasks') and immediately disambiguates scope: project tasks via projectId vs. personal tasks when omitted. This scoping detail distinguishes it from siblings like xtiles_get_task and xtiles_list_projects.

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?

Gives clear context for the primary branching decision (projectId present vs. absent) and lists optional filters. However, it doesn't reference alternatives like xtiles_get_task or xtiles_search_projects, nor when-not to use this tool.

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

All xTiles 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.

Resources

Need Help?