Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

create_project

Create a new project in Zoho Projects by specifying name, description, dates, and visibility settings to organize work and track progress.

Instructions

Create a new project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProject name
descriptionNoProject description
start_dateNoStart date (YYYY-MM-DD)
end_dateNoEnd date (YYYY-MM-DD)
is_publicNoIs project public

Implementation Reference

  • Handler function that executes the create_project tool by sending a POST request to the Zoho Projects API to create a new project using the provided parameters.
    private async createProject(params: any) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects`,
        "POST",
        params
      );
      return {
        content: [
          {
            type: "text",
            text: `Project created successfully:\n${JSON.stringify(data, null, 2)}`,
          },
        ],
      };
    }
  • Handler function that executes the create_project tool by sending a POST request to the Zoho Projects API to create a new project using the provided parameters.
    private async createProject(params: any) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects`,
        "POST",
        params
      );
      return {
        content: [
          {
            type: "text",
            text: `Project created successfully:\n${JSON.stringify(data, null, 2)}`,
          },
        ],
      };
    }
  • Input schema definition for the create_project tool, specifying required 'name' and optional fields like description, dates, and public status.
      name: "create_project",
      description: "Create a new project",
      inputSchema: {
        type: "object",
        properties: {
          name: { type: "string", description: "Project name" },
          description: { type: "string", description: "Project description" },
          start_date: {
            type: "string",
            description: "Start date (YYYY-MM-DD)",
          },
          end_date: { type: "string", description: "End date (YYYY-MM-DD)" },
          is_public: {
            type: "boolean",
            description: "Is project public",
            default: false,
          },
        },
        required: ["name"],
      },
    },
    {
  • Input schema definition for the create_project tool, specifying required 'name' and optional fields like description, dates, and public status.
    {
      name: "create_project",
      description: "Create a new project",
      inputSchema: {
        type: "object",
        properties: {
          name: { type: "string", description: "Project name" },
          description: { type: "string", description: "Project description" },
          start_date: {
            type: "string",
            description: "Start date (YYYY-MM-DD)",
          },
          end_date: { type: "string", description: "End date (YYYY-MM-DD)" },
          is_public: {
            type: "boolean",
            description: "Is project public",
            default: false,
          },
        },
        required: ["name"],
      },
    },
  • Registration in the tool dispatch switch statement that routes calls to create_project to the handler method.
    case "create_project":
      return await this.createProject(params);
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 a new project', implying a write/mutation operation, but doesn't cover critical aspects like required permissions, whether creation is idempotent, error handling, or what happens on success (e.g., returns a project ID). This leaves significant gaps for an agent to understand the tool's behavior.

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 with a single sentence ('Create a new project'), which is front-loaded and wastes no words. While it may be under-informative, it scores high on conciseness as every word earns its place without redundancy.

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 complexity of a creation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the tool's behavior, usage context, or expected outcomes, leaving the agent with insufficient information to use it effectively beyond the basic schema.

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?

The input schema has 100% description coverage, with clear parameter names and descriptions (e.g., 'name' as project name, 'start_date' in YYYY-MM-DD format). The tool description adds no parameter-specific information beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Create') and resource ('project'), making the basic purpose clear. However, it lacks specificity about what a 'project' entails in this context and doesn't differentiate from sibling tools like 'create_phase' or 'create_task', which suggests similar creation operations for different resources.

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 prerequisites, when to choose 'create_project' over 'update_project', or how it relates to other creation tools like 'create_issue' or 'create_task'. The description offers no context for decision-making.

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