ClickUp MCP Server

Overview Schema Source Related Servers Discussions Admin

get_task

Retrieve detailed information for a specific ClickUp task using its ID, with options to include subtasks and markdown description.

Instructions

Get details of a single ClickUp task.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "get_task"
  }
}

Input Schema

Name	Required	Description
`task_id`	Yes	The ID of the task
`include_subtasks`	No	Include subtasks in response
`include_markdown_description`	No	Include markdown description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 4, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are present, so the description carries the burden. It only states a read operation ('Get details') without disclosing response structure, error behavior, or effects of optional parameters. However, for a simple get operation, this is adequate and not misleading.

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 one efficient sentence of eight words, directly stating the purpose without any redundant phrasing. It is front-loaded and easy to parse.

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

Completeness3/5

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

For a simple fetch-by-ID tool, the description is adequate, but it lacks specificity about what 'details' includes (e.g., returned fields) since no output schema exists. Optional parameters are covered in the schema, but the description doesn't contextualize them. The tool's simplicity mitigates this gap.

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?

Input schema covers 100% of parameters, each with clear descriptions. The tool description adds no additional parameter context, so it relies fully on the schema. Baseline 3 is appropriate.

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 the tool retrieves details for a single task, using the verb 'Get' and the resource 'details of a single ClickUp task.' The word 'single' distinguishes it from the sibling get_tasks, making the purpose specific and unambiguous.

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?

Usage is implied by the singular 'task' and required task_id parameter, but no explicit alternatives or when-not-to-use guidance is provided. It doesn't mention that get_tasks should be used for multiple tasks, leaving the guidance purely implicit.

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

Deploy Server