Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

search

Search across Zoho Projects portal or specific projects to find tasks, issues, milestones, forums, and events using keywords and filters.

Instructions

Search across portal or project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
search_termYesSearch term/query
project_idNoProject ID (optional for portal-level search)
moduleNoModule to search in
pageNoPage number
per_pageNoItems per page

Implementation Reference

  • The handler function that executes the 'search' tool. It destructures parameters, builds the appropriate Zoho API search endpoint (project-specific or portal-wide), calls makeRequest to fetch results, and returns the JSON-formatted response as MCP content.
    private async search(params: any) {
      const { search_term, project_id, module = "all", page = 1, per_page = 10 } = params;
      const endpoint = project_id
        ? `/portal/${this.config.portalId}/projects/${project_id}/search?search_term=${encodeURIComponent(search_term)}&module=${module}&page=${page}&per_page=${per_page}`
        : `/portal/${this.config.portalId}/search?search_term=${encodeURIComponent(search_term)}&module=${module}&status=active&page=${page}&per_page=${per_page}`;
      const data = await this.makeRequest(endpoint);
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • The input schema defining parameters for the 'search' tool: search_term (required), project_id (optional), module (enum), page, per_page.
    inputSchema: {
      type: "object",
      properties: {
        search_term: {
          type: "string",
          description: "Search term/query",
        },
        project_id: {
          type: "string",
          description: "Project ID (optional for portal-level search)",
        },
        module: {
          type: "string",
          description: "Module to search in",
          enum: [
            "all",
            "projects",
            "tasks",
            "issues",
            "milestones",
            "forums",
            "events",
          ],
        },
        page: { type: "number", description: "Page number", default: 1 },
        per_page: {
          type: "number",
          description: "Items per page",
          default: 10,
        },
      },
      required: ["search_term"],
  • src/index.ts:489-525 (registration)
    The tool registration object in the listTools response, specifying name 'search', description, and inputSchema.
    {
      name: "search",
      description: "Search across portal or project",
      inputSchema: {
        type: "object",
        properties: {
          search_term: {
            type: "string",
            description: "Search term/query",
          },
          project_id: {
            type: "string",
            description: "Project ID (optional for portal-level search)",
          },
          module: {
            type: "string",
            description: "Module to search in",
            enum: [
              "all",
              "projects",
              "tasks",
              "issues",
              "milestones",
              "forums",
              "events",
            ],
          },
          page: { type: "number", description: "Page number", default: 1 },
          per_page: {
            type: "number",
            description: "Items per page",
            default: 10,
          },
        },
        required: ["search_term"],
      },
    },
  • src/index.ts:600-602 (registration)
    The dispatch case in the CallToolRequest handler that routes 'search' tool calls to the search handler function.
    case "search":
      return await this.search(params);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the burden, but it only restates the purpose. It fails to disclose read-only behavior, pagination, result format, or any side effects, leaving the agent without essential behavioral context.

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 concise sentence with no extraneous words. It is immediately clear and front-loaded.

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?

Despite having 5 parameters and no output schema, the description gives no insight into how the search behaves, what it returns, or how scope (portal vs project) is determined. The minimal description is insufficient for a tool with this complexity.

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 coverage is 100%, and each parameter has a description, so the baseline of 3 applies. The description adds no additional parameter semantics beyond what the schema already provides.

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 states a clear action (Search) and a scoped resource (portal or project), which distinguishes it from sibling list/get tools. However, it doesn't specify the breadth of searchable content, relying on the schema's module enum for that.

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 directly fetching a known resource (e.g., get_project, get_task). No exclusions or alternative tool mentions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.