Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

create_task

Add a new task to a Zoho Projects project by specifying name, description, priority, dates, and assignee to organize project work.

Instructions

Create a new task in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
nameYesTask name
descriptionNoTask description
priorityNoTask priority
start_dateNoStart date (YYYY-MM-DD)
end_dateNoEnd date (YYYY-MM-DD)
assignee_zpuidNoAssignee user ZPUID

Implementation Reference

  • The handler function that executes the create_task tool. It extracts project_id and task data from params, makes a POST request to the Zoho Projects API to create the task, and returns a formatted MCP response with the created task details.
    private async createTask(params: any) {
      const { project_id, ...taskData } = params;
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${project_id}/tasks`,
        "POST",
        taskData
      );
      return {
        content: [
          {
            type: "text",
            text: `Task created successfully:\n${JSON.stringify(data, null, 2)}`,
          },
        ],
      };
    }
  • The input schema definition for the create_task tool, defining parameters like project_id, name, description, priority, dates, and assignee.
    {
      name: "create_task",
      description: "Create a new task in a project",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { type: "string", description: "Project ID" },
          name: { type: "string", description: "Task name" },
          description: { type: "string", description: "Task description" },
          priority: {
            type: "string",
            description: "Task priority",
            enum: ["none", "low", "medium", "high"],
          },
          start_date: {
            type: "string",
            description: "Start date (YYYY-MM-DD)",
          },
          end_date: { type: "string", description: "End date (YYYY-MM-DD)" },
          assignee_zpuid: {
            type: "string",
            description: "Assignee user ZPUID",
          },
        },
        required: ["project_id", "name"],
      },
    },
  • src/index.ts:576-577 (registration)
    The switch case registration that dispatches calls to the createTask handler.
    case "create_task":
      return await this.createTask(params);
  • Duplicate handler function for the create_task tool in the HTTP server version, identical implementation to src/index.ts.
    private async createTask(params: any) {
      const { project_id, ...taskData } = params;
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${project_id}/tasks`,
        "POST",
        taskData
      );
      return {
        content: [
          {
            type: "text",
            text: `Task created successfully:\n${JSON.stringify(data, null, 2)}`,
          },
        ],
      };
    }
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 it creates a task without disclosing behavioral traits like permissions needed, whether it's idempotent, error handling, or what happens on success (e.g., returns a task ID). This is inadequate for a mutation 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 no wasted words, making it easy to parse. It's appropriately sized and front-loaded with the core action, earning its place without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral nuances, leaving significant gaps in understanding how to use it effectively in context.

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%, so the schema fully documents all 7 parameters. The description adds no additional meaning beyond implying creation, which is already clear from the tool name. Baseline score of 3 is appropriate as 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 ('Create') and resource ('new task in a project'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_issue' or 'create_phase' which also create items in similar contexts, missing explicit distinction.

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 like 'create_issue' or 'create_phase', nor does it mention prerequisites such as needing an existing project. It simply states what it does without context for selection.

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/qpiai/zoho-projects-mcp'

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