Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

list_projects

Retrieve all projects from your Zoho Projects portal to view and manage your project portfolio.

Instructions

List all projects in a portal

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
per_pageNoItems per page

Implementation Reference

  • Core handler function executing the list_projects tool by making an authenticated API request to Zoho Projects to retrieve paginated list of projects and returning formatted JSON response.
    private async listProjects(page: number = 1, perPage: number = 10) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects?page=${page}&per_page=${perPage}`
      );
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • src/index.ts:202-215 (registration)
    Registration of the list_projects tool in the tools list returned by ListToolsRequestSchema, including name, description, and input schema.
      name: "list_projects",
      description: "List all projects in a portal",
      inputSchema: {
        type: "object",
        properties: {
          page: { type: "number", description: "Page number", default: 1 },
          per_page: {
            type: "number",
            description: "Items per page",
            default: 10,
          },
        },
      },
    },
  • Core handler function executing the list_projects tool by making an authenticated API request to Zoho Projects to retrieve paginated list of projects and returning formatted JSON response.
    private async listProjects(page: number = 1, perPage: number = 10) {
      const data = await this.makeRequest(
        `/portal/${this.config.portalId}/projects?page=${page}&per_page=${perPage}`
      );
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Registration of the list_projects tool in the tools list returned by ListToolsRequestSchema, including name, description, and input schema.
      name: "list_projects",
      description: "List all projects in a portal",
      inputSchema: {
        type: "object",
        properties: {
          page: { type: "number", description: "Page number", default: 1 },
          per_page: {
            type: "number",
            description: "Items per page",
            default: 10,
          },
        },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't mention pagination behavior (implied by parameters but not described), authentication requirements, rate limits, or what constitutes 'all projects' (active only, archived, etc.). The description lacks crucial context about how this operation behaves.

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 - a single sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core functionality and wastes no space on redundant information or verbose explanations.

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 list operation with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what information is returned about projects, whether the list is filtered or sorted, or how to interpret the pagination parameters in practice. The agent would need to guess about the tool's behavior and output format.

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?

With 100% schema description coverage, the input schema already documents both parameters (page and per_page) with their types and defaults. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline for high schema coverage without compensating with extra semantic context.

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 ('List all projects') and resource ('in a portal'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from similar sibling tools like 'list_issues' or 'list_tasks' - it only specifies the resource type but not how it differs from other list operations.

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. With sibling tools like 'get_project' (for retrieving a specific project), 'search' (for filtered queries), and 'list_portals' (for listing portals rather than projects), there's no indication of when this unfiltered list operation is appropriate versus more targeted alternatives.

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