Skip to main content
Glama
qpiai

Zoho Projects MCP Server

by qpiai

list_tasks

Retrieve and display tasks from Zoho Projects, allowing users to view project or portal-level task lists with pagination controls.

Instructions

List tasks 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 implements the core logic for the 'list_tasks' tool. It builds the Zoho Projects API endpoint depending on whether a project ID is provided (project-specific or portal-wide tasks) and fetches the data using the shared makeRequest method, returning formatted JSON.
    private async listTasks(
      projectId?: string,
      page: number = 1,
      perPage: number = 10
    ) {
      const endpoint = projectId
        ? `/portal/${this.config.portalId}/projects/${projectId}/tasks?page=${page}&per_page=${perPage}`
        : `/portal/${this.config.portalId}/tasks?page=${page}&per_page=${perPage}`;
      const data = await this.makeRequest(endpoint);
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • The tool schema definition including name, description, and input schema for parameters (project_id optional, pagination). This is returned by the ListTools handler.
    {
      name: "list_tasks",
      description: "List tasks 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:572-573 (registration)
    Registration/dispatch point in the CallToolRequestSchema switch statement that routes calls to the listTasks handler.
    case "list_tasks":
      return await this.listTasks(params.project_id, params.page, params.per_page);
  • Identical handler function in the HTTP server implementation for the 'list_tasks' tool.
    private async listTasks(
      projectId?: string,
      page: number = 1,
      perPage: number = 10
    ) {
      const endpoint = projectId
        ? `/portal/${this.config.portalId}/projects/${projectId}/tasks?page=${page}&per_page=${perPage}`
        : `/portal/${this.config.portalId}/tasks?page=${page}&per_page=${perPage}`;
      const data = await this.makeRequest(endpoint);
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • Identical tool schema in the HTTP server version.
    {
      name: "list_tasks",
      description: "List tasks 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,
          },
        },
      },
    },
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 limited behavioral insight. It implies a read-only operation (listing) but doesn't disclose pagination behavior (beyond what the schema shows), rate limits, authentication needs, or what happens if project_id is omitted. For a tool with 3 parameters and no annotation coverage, this is inadequate.

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 that front-loads the core purpose. Every word earns its place, with no redundant or vague phrasing. It's appropriately sized for a simple list operation.

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 the tool's complexity (3 parameters, no output schema, no annotations), the description is incomplete. It lacks details on return format, error conditions, pagination behavior, and how it differs from sibling tools like search. For a list operation in a system with multiple query options, more context 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 the schema fully documents all parameters. The description adds marginal value by clarifying that project_id is optional for portal-level listing, but doesn't provide additional context like format examples or interaction effects between parameters. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('List') and resource ('tasks'), and specifies the scope ('from a project or portal'). It distinguishes itself from other list tools like list_issues or list_projects by focusing on tasks. However, it doesn't explicitly differentiate from get_task (which retrieves a single task) or search (which might find tasks), so it's not a perfect 5.

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 minimal guidance: it mentions the optional project_id for portal-level listing, but doesn't specify when to use this tool versus alternatives like get_task (for single tasks), search (for filtered queries), or list_issues (for related resources). No explicit when-not-to-use or prerequisite information is given.

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