Skip to main content
Glama
rafliruslan

TickTick MCP Server

by rafliruslan

get_projects

Retrieve all projects from TickTick task management to organize and access your work lists.

Instructions

Get all projects from TickTick

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_projects' tool in the MCP server request handler. It calls the TickTickClient's getProjects method and returns the projects as a JSON string in the response content.
    case 'get_projects':
      const projects = await this.ticktickClient!.getProjects();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(projects, null, 2),
          },
        ],
      };
  • Zod schema definition for TickTickProject, used as the type for projects returned by getProjects.
    export const TickTickProjectSchema = z.object({
      id: z.string(),
      name: z.string(),
      color: z.string().optional(),
      inAll: z.boolean().optional(),
      sortOrder: z.number().optional(),
      sortType: z.string().optional(),
      userCount: z.number().optional(),
      etag: z.string().optional(),
      modifiedTime: z.string().optional(),
      closed: z.boolean().optional(),
      muted: z.boolean().optional(),
      transferred: z.boolean().optional(),
      groupId: z.string().optional(),
      viewMode: z.string().optional(),
      notificationOptions: z.object({
        beMentioned: z.boolean().optional(),
        newTaskAssignedToMe: z.boolean().optional(),
        newTaskCreated: z.boolean().optional(),
        taskCompleted: z.boolean().optional(),
        taskDeleted: z.boolean().optional(),
        taskUpdated: z.boolean().optional()
      }).optional(),
      teamId: z.string().optional(),
      permission: z.string().optional(),
      kind: z.string().optional()
    });
  • src/index.ts:82-89 (registration)
    Registration of the 'get_projects' tool in the MCP tools list, including name, description, and empty input schema.
    {
      name: 'get_projects',
      description: 'Get all projects from TickTick',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Core implementation of getProjects in TickTickClient class, which authenticates and makes an API GET request to '/project' to fetch the list of projects.
    async getProjects(): Promise<TickTickProject[]> {
      await this.ensureAuthenticated();
      
      try {
        const response = await this.client.get('/project');
        return response.data || [];
      } catch (error) {
        throw new Error(`Failed to get projects: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get all projects' but doesn't describe what 'all' entails (e.g., pagination, filtering, or sorting), the response format, error conditions, or any rate limits. This leaves significant gaps in understanding how the tool behaves.

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 no wasted words. It front-loads the key information ('Get all projects') and avoids unnecessary elaboration, 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., project list format, fields included) or any behavioral nuances. For a tool with no structured output documentation, this leaves the agent with insufficient context to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, earning a baseline score of 4 for adequately handling the lack of parameters.

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 all projects') and the resource ('from TickTick'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get_tasks' or 'get_task' beyond mentioning 'projects' versus '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 prerequisites, context for retrieving projects versus tasks, or any exclusions. The agent must infer usage based solely on the tool name and description.

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