Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

create_issue

Create new issues in Zoho Projects by specifying project ID, title, description, severity, and due date to track and manage project problems.

Instructions

Create a new issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
titleYesIssue title
descriptionNoIssue description
severityNoIssue severity
due_dateNoDue date (YYYY-MM-DD)

Implementation Reference

  • Core handler function that destructures params, calls makeRequest to POST new issue data to Zoho Projects API endpoint, and returns formatted success response with created issue details.
    private async createIssue(params: any) {
      const { project_id, ...issueData } = params;
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${project_id}/issues`,
        "POST",
        issueData
      );
      return {
        content: [
          {
            type: "text",
            text: `Issue created successfully:\n${JSON.stringify(data, null, 2)}`,
          },
        ],
      };
  • Core handler function that destructures params, calls makeRequest to POST new issue data to Zoho Projects API endpoint, and returns formatted success response with created issue details.
    private async createIssue(params: any) {
      const { project_id, ...issueData } = params;
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${project_id}/issues`,
        "POST",
        issueData
      );
      return {
        content: [
          {
            type: "text",
            text: `Issue created successfully:\n${JSON.stringify(data, null, 2)}`,
          },
        ],
      };
  • Input schema defining parameters for create_issue tool: project_id and title required, optional description, severity (enum), due_date.
    inputSchema: {
      type: "object",
      properties: {
        project_id: { type: "string", description: "Project ID" },
        title: { type: "string", description: "Issue title" },
        description: { type: "string", description: "Issue description" },
        severity: {
          type: "string",
          description: "Issue severity",
          enum: ["minor", "major", "critical"],
        },
        due_date: { type: "string", description: "Due date (YYYY-MM-DD)" },
      },
      required: ["project_id", "title"],
    },
  • Registration of create_issue tool in the tools list returned by listTools, specifying name, description, and input schema.
    {
      name: "create_issue",
      description: "Create a new issue",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { type: "string", description: "Project ID" },
          title: { type: "string", description: "Issue title" },
          description: { type: "string", description: "Issue description" },
          severity: {
            type: "string",
            description: "Issue severity",
            enum: ["minor", "major", "critical"],
          },
          due_date: { type: "string", description: "Due date (YYYY-MM-DD)" },
        },
        required: ["project_id", "title"],
      },
    },
  • Dispatch case in CallToolRequestHandler switch statement that routes 'create_issue' calls to the handler method.
    case "create_issue":
      return await this.createIssue(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. 'Create a new issue' implies a write operation, but it doesn't specify permissions needed, whether it's idempotent, error handling, or what happens on success/failure. This is a significant gap 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 extremely concise with just three words, front-loading the core purpose without any wasted text. Every word earns its place, though this conciseness comes at the cost of completeness.

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 5 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what an 'issue' is in this system, what happens after creation, or provide any context beyond the bare minimum. More information is needed given the complexity and lack of structured data.

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 descriptions and constraints. The description adds no additional meaning beyond what's in the schema, such as explaining relationships between parameters or usage examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Create a new issue' clearly states the action (create) and resource (issue), but it's vague about what an 'issue' entails in this context and doesn't distinguish it from sibling tools like 'create_task' or 'create_project'. It provides basic purpose but lacks specificity about the domain or scope.

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 like 'create_task' or 'update_issue'. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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