Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_task

Read-onlyIdempotent

Retrieve a single task's full details by its ID, including subtasks and markdown description.

Instructions

Fetch one task by id.

Calls GET /task/{task_id}. Set custom_task_ids=true (plus team_id / CLICKUP_TEAM_ID) to look the task up by its Custom Task ID. Optionally pull subtasks and a markdown description.

When to Use:

  • To read a single task's full detail when you already have its id.

When NOT to Use:

  • To browse or search many tasks — use clickup_get_tasks (one List) or clickup_get_filtered_team_tasks (whole Workspace).

Returns: Markdown detail (name, status, priority, assignees, dates, description) or the raw task JSON when response_format="json".

Examples:

  • params = {"task_id": "86cxy1", "include_subtasks": true}

  • By custom id: params = {"task_id": "PROJ-42", "custom_task_ids": true, "team_id": "9000"}

Error Handling: 404 means the id is wrong (or you passed a Custom Task ID without custom_task_ids=true).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable details about return format (markdown or json), custom task ID behavior, and error handling (404 meaning wrong id), going beyond what annotations provide.

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?

The description is well-organized with clear sections, front-loading the core purpose. Every sentence adds value, and the structure makes it easy to scan for key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all necessary aspects: purpose, usage conditions, alternatives, parameter details, return values, and error scenarios. Given the tool's simplicity and the presence of an output schema, the description is fully sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains the interplay between custom_task_ids and team_id, offers examples for both standard and custom ID usage, and clarifies the response_format parameter. This adds significant context beyond the schema descriptions, especially given that schema description coverage is 0% per context signals.

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 'Fetch one task by id' and distinguishes itself from sibling tools by specifying when to use alternatives like clickup_get_tasks and clickup_get_filtered_team_tasks. It provides a specific verb and resource, making the purpose unambiguous.

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?

Explicitly includes 'When to Use' and 'When NOT to Use' sections, naming alternative tools for browsing or searching multiple tasks. Examples and error handling further guide correct usage.

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/trustxai/clickup-mcp'

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