Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

list_issues

Retrieve and display issues from Zoho Projects, allowing filtering by project ID and pagination for efficient issue management.

Instructions

List issues from a project or portal

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject ID (optional for portal-level)
pageNoPage number
per_pageNoItems per page

Implementation Reference

  • The handler function that executes the 'list_issues' tool logic by constructing the appropriate Zoho API endpoint based on project_id and pagination parameters, fetching data via makeRequest, and returning it as formatted text content.
    private async listIssues(
      projectId?: string,
      page: number = 1,
      perPage: number = 10
    ) {
      const endpoint = projectId
        ? `/portal/${this.config.portalId}/projects/${projectId}/issues?page=${page}&per_page=${perPage}`
        : `/portal/${this.config.portalId}/issues?page=${page}&per_page=${perPage}`;
      const data = await this.makeRequest(endpoint);
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Input schema definition for the 'list_issues' tool, specifying parameters project_id (optional), page, and per_page with types and descriptions.
    inputSchema: {
      type: "object",
      properties: {
        project_id: {
          type: "string",
          description: "Project ID (optional for portal-level)",
        },
        page: { type: "number", description: "Page number", default: 1 },
        per_page: {
          type: "number",
          description: "Items per page",
          default: 10,
        },
      },
    },
  • src/index.ts:381-399 (registration)
    Registration of the 'list_issues' tool in the MCP server's tools array, including name, description, and input schema.
    {
      name: "list_issues",
      description: "List issues from a project or portal",
      inputSchema: {
        type: "object",
        properties: {
          project_id: {
            type: "string",
            description: "Project ID (optional for portal-level)",
          },
          page: { type: "number", description: "Page number", default: 1 },
          per_page: {
            type: "number",
            description: "Items per page",
            default: 10,
          },
        },
      },
    },
  • src/index.ts:584-585 (registration)
    Tool dispatch in the request handler switch statement, routing 'list_issues' calls to the listIssues method.
    case "list_issues":
      return await this.listIssues(params.project_id, params.page, params.per_page);
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. It states it's a list operation but doesn't disclose behavioral traits like pagination behavior (implied by parameters but not described), rate limits, authentication needs, or what happens with invalid inputs. The description is minimal and lacks operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core function without waste. It's appropriately sized for a simple list tool, though it could be more front-loaded with key details. No redundant or verbose 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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., issue objects, pagination metadata), error conditions, or how it differs from siblings. For a list tool with pagination parameters, more context on behavior and output is needed.

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 parameters are fully documented in the schema. The description adds no additional meaning about parameters beyond implying 'project or portal' scope for 'project_id'. It doesn't explain parameter interactions or usage nuances, meeting the baseline for high schema coverage.

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 verb ('List') and resource ('issues'), but lacks specificity about scope or filtering. It mentions 'from a project or portal' which provides some context, but doesn't distinguish itself from sibling tools like 'get_issue' or 'search' that also retrieve issue data. The purpose is clear but generic.

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 explicit guidance on when to use this tool versus alternatives. The description mentions 'project or portal' scope, but doesn't clarify when to use 'list_issues' versus 'get_issue' (single issue) or 'search' (filtered search). No prerequisites, exclusions, or comparative context are provided.

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