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);
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. The description only states the scope but doesn't mention pagination behavior (implied by parameters), authentication needs, rate limits, response format, or error conditions. For a search tool with 5 parameters, this leaves significant 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 4 words, with zero wasted language. It's front-loaded with the core action and scope. While arguably too brief for completeness, as a standalone statement it's efficiently structured without redundancy.

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 search tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what types of results to expect, how results are structured, whether search is full-text or exact match, or any limitations. The minimal description leaves too many contextual gaps for effective tool 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 the schema already documents all 5 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters (e.g., how project_id interacts with module choices) or provide usage examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Search across portal or project' states the action (search) and scope (portal/project), but is vague about what resources are searched. It doesn't distinguish this from potential sibling search tools (none exist in the sibling list), but the scope specification is minimal. The purpose is understandable but lacks specificity about what 'across' means in terms of content types.

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 alternatives. The description mentions 'portal or project' scope but doesn't explain when to choose portal-level vs project-level search, nor does it reference any sibling tools for comparison. There's no mention of prerequisites, limitations, or typical use cases.

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