clickup_get_taskGet a single task by id. ClickUp REST: GET /task/{task_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | The task id. | |
| include_subtasks | No | Include the task's subtasks (serialized true/false). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, covering the read-only nature. The description adds the REST GET method and single-task scoping, but no further behavioral details such as error handling, response format, or effects of include_subtasks. Given annotation coverage, this is acceptable but minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that conveys the core purpose and REST endpoint without any wasted words. It is optimally concise while remaining informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with two documented parameters, the description is complete enough. There is no output schema, but the simple nature of the operation does not demand extensive return-value documentation. Slightly more context about what is returned could push it to 5, but it is adequate as is.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both task_id and include_subtasks fully described in the input schema. The description does not add any parameter-level meaning beyond the schema, so a baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get'), resource ('task'), and scope ('by id'), clearly distinguishing it from sibling tools like clickup_get_tasks which retrieves multiple tasks. The REST endpoint reference adds precision.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implicitly clarifies when to use this tool: when you have a task id and want a single task. It does not explicitly name alternatives or exclusion criteria, but the contrast with clickup_get_tasks is evident from the sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a unique resource+action combination, with clear scoping (e.g., get_tasks vs search_tasks differ by list vs workspace, list_lists vs list_folderless_lists by parent). No two tools appear to do the same thing, and the descriptions make boundaries explicit.
All tools follow a consistent verb_noun snake_case pattern (create_, get_, list_, search_, update_+resource), prefixed with clickup_. No camelCase or unconventional verbs are present.
14 tools is a well-scoped size for a project management API, covering hierarchy traversal (workspaces, spaces, folders, lists), task operations, comments, and user info. Each tool serves a clear purpose without unnecessary bloat.
The surface covers core CRUD for tasks (create, read, update) and comments, plus full hierarchy listing and search. Minor gaps include no delete task/comment and no update/list operations for folders/lists, but these are workable and don't hinder the primary workflows.