Skip to main content
Glama

get_task_details

Retrieve comprehensive task data from ClickUp: description, assignees, status, and dates. Use to view full task information.

Instructions

Get detailed information about a specific ClickUp task. Returns comprehensive task data including description, assignees, status, and dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe ID of the task to get
include_subtasksNoWhether to include subtasks in the task details

Implementation Reference

  • Actual handler that calls ClickUp API to get task details. Sends GET request to /task/{taskId} endpoint.
    async getTask(taskId: string, params?: { include_subtasks?: boolean }): Promise<Task> {
      return this.client.get(`/task/${taskId}`, params);
    }
  • TypeScript interface defining the shape of a Task object returned by the API.
    export interface Task {
      id: string;
      name: string;
      description?: string;
      status?: {
        status: string;
        color: string;
      };
      date_created?: string;
      date_updated?: string;
      date_closed?: string;
      creator?: {
        id: number;
        username: string;
        email: string;
      };
      assignees?: Array<{
        id: number;
        username: string;
        email: string;
      }>;
      priority?: {
        id: string;
        priority: string;
        color: string;
      };
      due_date?: string | null;
      start_date?: string | null;
      time_estimate?: number | null;
      time_spent?: number | null;
      custom_fields?: Array<any>;
      list?: {
        id: string;
        name: string;
      };
      folder?: {
        id: string;
        name: string;
      };
      space?: {
        id: string;
        name: string;
      };
      url: string;
      subtasks?: Task[]; // Add subtasks property
      parent?: string; // Add parent property
      top_level_parent?: string; // Add top_level_parent property
    }
  • Zod schema defining the input parameters for the get_task_details tool (task_id required, include_subtasks optional).
    {
      task_id: z.string().describe('The ID of the task to get'),
      include_subtasks: z.boolean().optional().describe('Whether to include subtasks in the task details')
    },
  • Registration of the get_task_details tool on the MCP server with schema and handler function.
    server.tool(
      'get_task_details',
      'Get detailed information about a specific ClickUp task. Returns comprehensive task data including description, assignees, status, and dates.',
      {
        task_id: z.string().describe('The ID of the task to get'),
        include_subtasks: z.boolean().optional().describe('Whether to include subtasks in the task details')
      },
      async ({ task_id, include_subtasks }) => {
        try {
          const task = await tasksClient.getTask(task_id, { include_subtasks });
          return {
            content: [{ type: 'text', text: JSON.stringify(task, null, 2) }]
          };
        } catch (error: any) {
          console.error('Error getting task details:', error);
          return {
            content: [{ type: 'text', text: `Error getting task details: ${error.message}` }],
            isError: true
          };
        }
      }
    );
  • src/index.ts:40-47 (registration)
    Server initialization that calls setupTaskTools, which registers all task tools including get_task_details on the MCP server.
    private setupTools() {
      // Set up all tools
      setupTaskTools(this.server);
      setupDocTools(this.server);
      setupSpaceTools(this.server);
      setupChecklistTools(this.server);
      setupCommentTools(this.server);
    }
Behavior2/5

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

No annotations. Description is minimal—does not disclose error handling, permissions, rate limits, or the full scope of returned data beyond a few examples.

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?

Two sentences, no fluff. Essential information is front-loaded.

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 get tool with two parameters, description is adequate but lacks output schema and behavioral details. Could be improved by noting possible errors or return format.

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 coverage is 100%; both parameters are already described. Description adds no additional meaning or usage tips beyond listing example return fields.

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?

Description clearly states it retrieves detailed information for a specific task, listing example fields. It distinguishes from siblings like get_tasks (list) and get_task_comments (comments).

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 over alternatives like get_tasks or get_task_comments. Agent must infer from name and parameters.

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

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