Skip to main content
Glama

get_task

Retrieve detailed information about a specific ClickUp task using its unique task ID to access task data and manage workflow.

Instructions

Get details of a ClickUp task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesClickUp Task ID

Implementation Reference

  • The main handler function for the 'get_task' tool. It makes a GET request to the ClickUp API using the provided task_id and returns the task details as JSON or an error message.
    const getTask = async (args: any) => {
      try {
        const response = await clickupApi.get(`/task/${args.task_id}`);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          return {
            content: [
              {
                type: "text",
                text: `ClickUp API error: ${error.response?.data?.err ?? error.message}`,
              },
            ],
            isError: true,
          };
        }
        throw error;
      }
    };
  • The schema definition for the 'get_task' tool, including description and inputSchema requiring 'task_id'.
    get_task: {
      description: "Get details of a ClickUp task",
      inputSchema: {
        type: "object",
        properties: {
          task_id: {
            type: "string",
            description: "ClickUp Task ID"
          }
        },
        required: ["task_id"]
      }
    }
  • src/index.ts:289-290 (registration)
    Registration of the 'get_task' tool in the CallToolRequestHandler switch statement, dispatching to the getTask handler.
    case 'get_task':
      return await getTask(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get details'), implying it's likely safe and non-destructive, but doesn't confirm this or address other behaviors like error handling, authentication needs, rate limits, or response format. This leaves significant gaps for a tool that interacts with external data.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loaded with the core action.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'details' are returned (e.g., task fields, status, assignees), error conditions, or how it differs from sibling tools. This leaves the agent with insufficient context to use the tool effectively beyond basic invocation.

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%, with the single parameter 'task_id' documented as 'ClickUp Task ID'. The description doesn't add any meaning beyond this (e.g., format examples, where to find the ID, or validation rules), so it meets the baseline for adequate but unenlightening parameter documentation.

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?

The description clearly states the verb ('Get details') and resource ('ClickUp task'), making the purpose specific and understandable. However, it doesn't distinguish this tool from its sibling 'get_tasks' (which likely retrieves multiple tasks), leaving some ambiguity about when to use each.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_tasks' or 'create_task'. It doesn't mention prerequisites (e.g., needing a valid task ID) or contextual factors that might influence tool selection.

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

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