Skip to main content
Glama
Leanware-io

ClickUp MCP Integration

by Leanware-io

clickup_get_task_by_custom_id

Retrieve ClickUp tasks using custom identifiers to access specific task details and information within your workspace.

Instructions

Get a task by its custom ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
custom_idYes

Implementation Reference

  • Tool handler for 'clickup_get_task_by_custom_id' that extracts custom_id from input and calls TaskService.getTaskByCustomId to fetch the task, returning JSON stringified response.
    const getTaskByCustomIdTool = defineTool((z) => ({
      name: "clickup_get_task_by_custom_id",
      description: "Get a task by its custom ID",
      inputSchema: {
        custom_id: z.string(),
      },
      handler: async (input) => {
        const { custom_id } = input;
        const response = await taskService.getTaskByCustomId(custom_id);
        return {
          content: [{ type: "text", text: JSON.stringify(response) }],
        };
      },
    }));
  • Input schema defining 'custom_id' as a required string.
    inputSchema: {
      custom_id: z.string(),
    },
  • Helper method in TaskService that performs the API GET request to ClickUp to retrieve task by custom ID using custom_task_ids=true parameter.
    async getTaskByCustomId(customId: string): Promise<ClickUpTask> {
      return this.request<ClickUpTask>(
        `/task/${customId}?custom_task_ids=true&team_id=${this.workspaceId}&include_subtasks=true&include_markdown_description=true`
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), implying non-destructive behavior, but lacks details on permissions, rate limits, error handling, or return format. This is inadequate for a tool with zero annotation coverage.

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 with zero wasted words. It's front-loaded with the core purpose, making it easy to parse quickly.

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 no annotations, no output schema, and low schema description coverage, the description is incomplete. It doesn't address behavioral traits, return values, or usage context, leaving significant gaps for an AI agent to operate effectively.

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 0%, but the description adds meaning by specifying that 'custom_id' identifies a task. However, it doesn't explain the format or constraints of the custom ID beyond what the schema's string type implies. With one parameter, the baseline is 4, but the minimal semantic addition lowers the score.

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 retrieval by custom ID. It distinguishes from sibling 'clickup_get_task' (likely by default ID) but doesn't explicitly contrast with 'clickup_update_task_by_custom_id' or other siblings.

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?

No guidance on when to use this tool versus alternatives like 'clickup_get_task' or 'clickup_update_task_by_custom_id'. The description implies usage when you have a custom ID, but doesn't specify prerequisites, exclusions, or contextual alternatives.

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