Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

list_portals

Retrieve all available Zoho Projects portals to access and manage your project workspaces through the MCP server.

Instructions

Retrieve all Zoho Projects portals

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function for the 'list_portals' tool. Makes an API request to Zoho's /portals endpoint and returns the response as formatted JSON text content.
    private async listPortals() {
      const data = await this.makeRequest("/portals");
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Identical core handler function for the 'list_portals' tool in the HTTP server variant.
    private async listPortals() {
      const data = await this.makeRequest("/portals");
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • src/index.ts:181-187 (registration)
    Tool registration entry in the listTools handler, including name, description, and schema.
      name: "list_portals",
      description: "Retrieve all Zoho Projects portals",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for the 'list_portals' tool, which requires no parameters.
    inputSchema: {
      type: "object",
      properties: {},
    },
  • src/index.ts:554-558 (registration)
    Dispatch/registration in the callTool request handler switch statement.
    case "list_portals":
      return await this.listPortals();
    case "get_portal":
      return await this.getPortal(params.portal_id);
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states 'Retrieve all' but doesn't disclose critical traits like whether it's paginated, requires authentication, has rate limits, or returns a specific format. This is inadequate for a 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 a single, efficient sentence with zero waste—it directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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, no output schema, and a simple tool (0 params), the description is incomplete. It lacks behavioral details (e.g., return format, pagination) and doesn't leverage the low complexity to provide fuller context, leaving gaps in understanding how the tool behaves.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, but that's acceptable here—baseline is 4 since the schema fully handles parameters, and the description doesn't need to compensate.

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 ('Retrieve') and resource ('all Zoho Projects portals'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_portal' (which likely retrieves a single portal) or 'list_projects' (which lists a different resource type), missing full sibling distinction.

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. It doesn't mention when to choose 'list_portals' over 'get_portal' (e.g., for bulk retrieval vs. single item) or other list tools like 'list_projects', leaving usage context implied at best.

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