Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

create_phase

Add a new phase or milestone to a Zoho Projects project by specifying project ID, phase name, dates, and owner to organize project timelines.

Instructions

Create a new phase/milestone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
nameYesPhase name
start_dateNoStart date (YYYY-MM-DD)
end_dateNoEnd date (YYYY-MM-DD)
owner_zpuidNoOwner user ZPUID

Implementation Reference

  • The handler function for the 'create_phase' tool. It extracts project_id and phaseData from input parameters, sends a POST request to the Zoho Projects API to create a new phase/milestone, and returns a formatted success response with the created phase details.
    private async createPhase(params: any) {
      const { project_id, ...phaseData } = params;
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${project_id}/phases`,
        "POST",
        phaseData
      );
      return {
        content: [
          {
            type: "text",
            text: `Phase created successfully:\n${JSON.stringify(data, null, 2)}`,
          },
        ],
      };
    }
  • src/index.ts:469-486 (registration)
    The registration of the 'create_phase' tool in the list_tools request handler, including its name, description, and input schema definition.
    {
      name: "create_phase",
      description: "Create a new phase/milestone",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { type: "string", description: "Project ID" },
          name: { type: "string", description: "Phase name" },
          start_date: {
            type: "string",
            description: "Start date (YYYY-MM-DD)",
          },
          end_date: { type: "string", description: "End date (YYYY-MM-DD)" },
          owner_zpuid: { type: "string", description: "Owner user ZPUID" },
        },
        required: ["project_id", "name"],
      },
    },
  • Input schema definition for the 'create_phase' tool, specifying required project_id and name, with optional dates and owner.
    inputSchema: {
      type: "object",
      properties: {
        project_id: { type: "string", description: "Project ID" },
        name: { type: "string", description: "Phase name" },
        start_date: {
          type: "string",
          description: "Start date (YYYY-MM-DD)",
        },
        end_date: { type: "string", description: "End date (YYYY-MM-DD)" },
        owner_zpuid: { type: "string", description: "Owner user ZPUID" },
      },
      required: ["project_id", "name"],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create' which implies a write/mutation operation, but doesn't address permissions, side effects, error conditions, or what happens on success (e.g., returns a phase ID). For a creation tool with zero annotation coverage, this is a significant gap in transparency.

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 4 words ('Create a new phase/milestone'), with zero wasted words. It's front-loaded with the core action and resource. Every word earns its place by clearly communicating the tool's purpose 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 creation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after creation, what permissions are needed, how it relates to existing phases, or what the tool returns. The agent would need to guess about important behavioral aspects not covered by the minimal description.

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 already documents all 5 parameters with their types and descriptions. The description adds no additional parameter information beyond what's in the schema. This meets the baseline of 3 for high schema coverage, but doesn't provide extra context like parameter relationships or examples.

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 phase/milestone'), making the purpose immediately understandable. It distinguishes this from sibling tools like create_project or create_task by specifying the type of entity being created. However, it doesn't explicitly contrast with list_phases or other phase-related tools, keeping it from a perfect score.

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 (e.g., needing an existing project), when not to use it, or how it relates to sibling tools like list_phases or update_project. This leaves the agent without contextual usage instructions.

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