Skip to main content
Glama
vitalio-sh

Enhanced Todoist MCP Server Extended

todoist_get_task

Retrieve a specific Todoist task using its unique ID to access details and manage task information within the Enhanced Todoist MCP Server Extended.

Instructions

Get a specific task by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe ID of the task to retrieve

Implementation Reference

  • Handler for todoist_get_task: validates input with isTaskIdArgs, calls todoistClient.getTask(taskId), formats response using formatTask, and returns formatted task details.
    if (name === "todoist_get_task") {
      if (!isTaskIdArgs(args)) {
        throw new Error("Invalid arguments for todoist_get_task");
      }
    
      const task = await todoistClient.getTask(args.taskId);
      return {
        content: [{ 
          type: "text", 
          text: `Task details:\nID: ${task.id}\n${formatTask(task)}` 
        }],
        isError: false,
      };
    }
  • Tool schema defining the input schema for todoist_get_task, requiring a taskId string.
    const GET_TASK_TOOL: Tool = {
      name: "todoist_get_task",
      description: "Get a specific task by its ID",
      inputSchema: {
        type: "object",
        properties: {
          taskId: {
            type: "string",
            description: "The ID of the task to retrieve"
          }
        },
        required: ["taskId"]
      }
    };
  • src/index.ts:1083-1122 (registration)
    Registration of the tool in the ListToolsRequestSchema handler by including GET_TASK_TOOL in the tools array returned to clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        // Task tools
        CREATE_TASK_TOOL,
        QUICK_ADD_TASK_TOOL,
        GET_TASKS_TOOL,
        GET_TASK_TOOL,
        UPDATE_TASK_TOOL,
        DELETE_TASK_TOOL,
        COMPLETE_TASK_TOOL,
        REOPEN_TASK_TOOL,
        SEARCH_TASKS_TOOL,
        MOVE_TASK_TOOL,
        BULK_MOVE_TASKS_TOOL,
        // Project tools
        GET_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        CREATE_PROJECT_TOOL,
        UPDATE_PROJECT_TOOL,
        DELETE_PROJECT_TOOL,
        // Section tools
        GET_SECTIONS_TOOL,
        CREATE_SECTION_TOOL,
        UPDATE_SECTION_TOOL,
        DELETE_SECTION_TOOL,
        // Label tools
        CREATE_LABEL_TOOL,
        GET_LABEL_TOOL,
        GET_LABELS_TOOL,
        UPDATE_LABEL_TOOL,
        DELETE_LABEL_TOOL,
        // Comment tools
        CREATE_COMMENT_TOOL,
        GET_COMMENT_TOOL,
        GET_COMMENTS_TOOL,
        UPDATE_COMMENT_TOOL,
        DELETE_COMMENT_TOOL,
      ],
    }));
  • Type guard helper function isTaskIdArgs used to validate arguments for todoist_get_task and similar task ID-based tools.
    function isTaskIdArgs(args: unknown): args is {
      taskId: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "taskId" in args &&
        typeof (args as { taskId: string }).taskId === "string"
      );
    }
  • Helper function formatTask used to format the task object into a readable string for output in todoist_get_task response.
    function formatTask(task: any): string {
      let taskDetails = `- ID: ${task.id}\n  Content: ${task.content}`;
      if (task.description) taskDetails += `\n  Description: ${task.description}`;
      if (task.due) taskDetails += `\n  Due: ${task.due.string}`;
      if (task.priority && task.priority > 1) taskDetails += `\n  Priority: ${task.priority}`;
      if (task.labels && task.labels.length > 0) taskDetails += `\n  Labels: ${task.labels.join(', ')}`;
      if (task.projectId) taskDetails += `\n  Project ID: ${task.projectId}`;
      if (task.sectionId) taskDetails += `\n  Section ID: ${task.sectionId}`;
      if (task.parentId) taskDetails += `\n  Parent ID: ${task.parentId}`;
      if (task.url) taskDetails += `\n  URL: ${task.url}`;
      if (task.commentCount > 0) taskDetails += `\n  Comments: ${task.commentCount}`;
      if (task.createdAt) taskDetails += `\n  Created At: ${task.createdAt}`;
      if (task.creatorId) taskDetails += `\n  Creator ID: ${task.creatorId}`;
      return taskDetails;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without behavioral details. It doesn't disclose if this is a read-only operation, what happens with invalid IDs (e.g., errors), authentication needs, rate limits, or response format, leaving significant gaps for an agent.

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 any unnecessary words. It's appropriately sized and front-loaded, 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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., task details, error handling), behavioral traits, or usage context, which are crucial for a tool that retrieves data by ID.

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 'taskId' fully documented in the schema as 'The ID of the task to retrieve'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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 action ('Get') and resource ('a specific task by its ID'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'todoist_get_tasks' (plural) which retrieves multiple tasks, leaving some ambiguity about when to use one versus the other.

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 is provided on when to use this tool versus alternatives. For example, it doesn't mention using 'todoist_get_tasks' for listing multiple tasks or 'todoist_search_tasks' for filtered searches, nor does it specify prerequisites like needing a valid task ID.

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/vitalio-sh/todoist-mcp-server-ext'

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