Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_get_task

Retrieve a specific ClickUp task by its ID to access task details and information within your workspace.

Instructions

Get a task by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes

Implementation Reference

  • Tool definition including name, description, input schema, and handler function for 'clickup_get_task'. The handler extracts task_id and calls taskService.getTask().
    const getTaskTool = defineTool((z) => ({
      name: "clickup_get_task",
      description: "Get a task by its ID",
      inputSchema: {
        task_id: z.string(),
      },
      handler: async (input) => {
        const { task_id } = input;
        const response = await taskService.getTask(task_id);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
  • Core implementation of fetching a task from ClickUp API using the private request method.
    async getTask(taskId: string): Promise<ClickUpTask> {
      return this.request<ClickUpTask>(
        `/task/${taskId}?custom_task_ids=false&team_id=${this.workspaceId}&include_subtasks=true&include_markdown_description=true`
      );
    }
  • src/index.ts:89-91 (registration)
    Registers the 'clickup_get_task' tool (along with others) on the MCP server by iterating over the tools array and calling server.tool.
    tools.forEach((tool) => {
      server.tool(tool.name, tool.description, tool.inputSchema, tool.handler);
    });
  • Zod input schema defining the required 'task_id' string parameter.
    inputSchema: {
      task_id: z.string(),
    },
  • Private request helper method used by getTask to make HTTP requests to ClickUp API.
    private async request<T>(
      endpoint: string,
      options: RequestInit = {}
    ): Promise<T> {
      const response = await fetch(`${BASE_URL}${endpoint}`, {
        ...options,
        headers: this.headers,
      });
      return response.json();
    }
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 it 'Get[s] a task,' implying a read-only operation, but fails to specify if it requires authentication, has rate limits, or what data is returned. For a tool with zero annotation coverage, this leaves critical behavioral traits unaddressed.

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 extremely concise—a single sentence with no wasted words. It front-loads the core action ('Get a task') and specifies the key input ('by its ID'), making it easy to parse quickly. Every part of the sentence serves a clear purpose.

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?

Given the complexity of a task retrieval tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't cover return values, error conditions, or behavioral aspects like permissions. For a tool that likely returns structured task data, this leaves significant gaps in understanding its full context.

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?

The schema description coverage is 0%, but the description adds meaning by specifying that 'task_id' is used to retrieve a task. However, it doesn't explain the format or constraints of 'task_id' beyond what the schema's type indicates. With one parameter and low coverage, it provides basic semantics but lacks depth, aligning with the baseline for minimal compensation.

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') and resource ('a task'), specifying it retrieves a task by its ID. It distinguishes from sibling tools like 'clickup_get_task_by_custom_id' by focusing on the standard ID, though it doesn't explicitly mention this distinction. The purpose is specific and actionable, avoiding tautology.

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, such as 'clickup_get_task_by_custom_id' for tasks identified by custom IDs or 'clickup_update_task' for modifications. It lacks context on prerequisites or scenarios, offering only a basic functional statement without usage instructions.

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

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