Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

update_issue

Modify existing issues in Zoho Projects by updating title, description, severity, or other fields to reflect current project status and requirements.

Instructions

Update an issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID
issue_idYesIssue ID
titleNoIssue title
descriptionNoIssue description
severityNoIssue severity

Implementation Reference

  • The handler function for 'update_issue' tool. It extracts project_id, issue_id, and other update data from params, makes a PATCH request to the Zoho API endpoint for updating the issue, and returns a success message with the API response.
    private async updateIssue(params: any) {
      const { project_id, issue_id, ...issueData } = params;
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects/${project_id}/issues/${issue_id}`,
        "PATCH",
        issueData
      );
      return {
        content: [
          {
            type: "text",
            text: `Issue updated successfully:\n${JSON.stringify(data, null, 2)}`,
          },
        ],
      };
    }
  • The input schema definition for the 'update_issue' tool, specifying required project_id and issue_id, and optional fields like title, description, severity.
    {
      name: "update_issue",
      description: "Update an issue",
      inputSchema: {
        type: "object",
        properties: {
          project_id: { type: "string", description: "Project ID" },
          issue_id: { type: "string", description: "Issue ID" },
          title: { type: "string", description: "Issue title" },
          description: { type: "string", description: "Issue description" },
          severity: {
            type: "string",
            description: "Issue severity",
            enum: ["minor", "major", "critical"],
          },
        },
        required: ["project_id", "issue_id"],
      },
    },
  • src/index.ts:590-591 (registration)
    The switch case in the CallToolRequestSchema handler that registers and dispatches the 'update_issue' tool call to its handler function.
    case "update_issue":
      return await this.updateIssue(params);
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Update an issue' implies a mutation operation but doesn't specify what happens during the update (e.g., whether all fields must be provided, if partial updates are supported, what permissions are required, or what the response contains). For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects undocumented.

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 three words, with zero wasted language. It's front-loaded with the core action. While this conciseness comes at the expense of completeness, the description itself doesn't contain any redundant or unnecessary elements.

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 the tool returns, what happens during execution, or provide any context about the update operation. The 100% schema coverage helps with parameters, but the overall description fails to provide sufficient context for safe and effective use.

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 all parameters are documented in the schema itself. The description adds no parameter information beyond what's already in the structured fields. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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

Purpose2/5

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

The description 'Update an issue' is a tautology that merely restates the tool name without adding meaningful context. It doesn't specify what aspects of an issue can be updated or distinguish this tool from sibling update tools like update_project or update_task. While the verb 'update' is clear, the description lacks specificity about the resource 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 Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance about when to use this tool versus alternatives. It doesn't mention prerequisites (like needing an existing issue), when to choose update_issue over create_issue or get_issue, or any constraints on usage. With multiple sibling tools available, this absence of contextual guidance is problematic.

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