Skip to main content
Glama
rafliruslan

TickTick MCP Server

by rafliruslan

get_task

Retrieve a specific task from TickTick using its task ID and project ID to access detailed task information for management or review.

Instructions

Get a specific task by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesTask ID to retrieve (required)
projectIdYesProject ID containing the task (required)

Implementation Reference

  • MCP handler for 'get_task' tool: validates taskId and projectId, fetches task using TickTickClient.getTaskById, returns JSON stringified task.
    case 'get_task':
      if (!args?.taskId || !args?.projectId) {
        throw new McpError(ErrorCode.InvalidParams, 'Task ID and Project ID are required');
      }
      const task = await this.ticktickClient!.getTaskById(args.taskId as string, args.projectId as string);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(task, null, 2),
          },
        ],
      };
  • src/index.ts:196-213 (registration)
    Registration of 'get_task' tool in ListTools handler, defining name, description, and input schema.
    {
      name: 'get_task',
      description: 'Get a specific task by ID',
      inputSchema: {
        type: 'object',
        properties: {
          taskId: {
            type: 'string',
            description: 'Task ID to retrieve (required)',
          },
          projectId: {
            type: 'string',
            description: 'Project ID containing the task (required)',
          },
        },
        required: ['taskId', 'projectId'],
      },
    },
  • TickTickClient method implementing the API call to retrieve a specific task by projectId and taskId.
    async getTaskById(taskId: string, projectId: string): Promise<TickTickTask> {
      await this.ensureAuthenticated();
      
      try {
        const response = await this.client.get(`/project/${projectId}/task/${taskId}`);
        return response.data;
      } catch (error) {
        throw new Error(`Failed to get task: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation ('Get'), implying it's read-only, but doesn't explicitly confirm this or mention any behavioral traits like error handling, authentication requirements, rate limits, or what happens if the task doesn't exist. The description is minimal and lacks important operational context.

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 at just 6 words. It's front-loaded with the core purpose and wastes no words. Every word earns its place in communicating the essential function.

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 this is a retrieval tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what information is returned, how errors are handled, or any operational constraints. For a tool that presumably returns task details, the description should provide more context about the retrieval operation and expected outcomes.

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 both parameters clearly documented in the schema. The description doesn't add any meaningful parameter information beyond what's already in the schema. It mentions 'by ID' which aligns with the taskId parameter, but provides no additional context about parameter relationships, formats, or constraints.

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 tool's purpose as 'Get a specific task by ID', which is a specific verb+resource combination. It distinguishes from siblings like 'get_tasks' (plural) by specifying retrieval of a single task, but doesn't explicitly contrast with other retrieval siblings like 'get_overdue_tasks' or 'get_todays_tasks'.

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. It doesn't mention when this tool is appropriate versus using 'get_tasks' for multiple tasks, or how it relates to other retrieval tools like 'get_overdue_tasks'. There's no context about prerequisites or exclusions.

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/rafliruslan/ticktick-mcp-server'

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