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,
          },
        },
      },
    },

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

There are no annotations, and the description only states 'List tasks' without disclosing behavior such as pagination defaults, ordering, permissions, or whether results are scoped by portal/project. It adds minimal value beyond the tool's name.

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?

One short sentence front-loaded with the main action, no filler words. Appropriate length and structure for a simple list operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple listing nature, the description is adequate but sparse. It lacks any mention of return format or additional filters beyond what the schema provides, and with no output schema, the agent must infer the response structure.

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?

The input schema provides 100% parameter coverage (page, per_page, project_id), and the description offers no additional parameter context. The phrase 'from a project or portal' hints at project_id's optionality but the schema already states that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'List' with the resource 'tasks' and clearly states scope ('from a project or portal'), distinguishing it from sibling tools like list_issues and list_projects.

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 on when to use this tool versus alternatives like search or get_task_by_prefix. It only states what it does, without clarifying exclusions or preferred use cases.

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