Skip to main content
Glama
makeplane

Plane MCP Server

Official
by makeplane

list_module_issues

Retrieve all issues associated with a specific module in a project using the project and module UUID identifiers. Ideal for managing and analyzing module-related tasks within Plane's project management system.

Instructions

Get all issues for a specific module

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_idYesThe uuid identifier of the module to get issues for
project_idYesThe uuid identifier of the project containing the module

Implementation Reference

  • The handler function that executes the tool: makes a GET request to the Plane API for module issues and returns the JSON response as text content.
    async ({ project_id, module_id }) => {
      const response = await makePlaneRequest(
        "GET",
        `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/modules/${module_id}/module-issues/`
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • Input schema defined with Zod for project_id and module_id parameters.
    {
      project_id: z.string().describe("The uuid identifier of the project containing the module"),
      module_id: z.string().describe("The uuid identifier of the module to get issues for"),
    },
  • Registration of the list_module_issues tool on the MCP server, including schema and handler.
    server.tool(
      "list_module_issues",
      "Get all issues for a specific module",
      {
        project_id: z.string().describe("The uuid identifier of the project containing the module"),
        module_id: z.string().describe("The uuid identifier of the module to get issues for"),
      },
      async ({ project_id, module_id }) => {
        const response = await makePlaneRequest(
          "GET",
          `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/modules/${module_id}/module-issues/`
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      }
    );
  • Invocation of registerModuleIssueTools within the main registerTools function.
    registerModuleIssueTools(server);
  • Helper function makePlaneRequest used by the handler to make authenticated HTTP requests to the Plane API.
    export async function makePlaneRequest<T>(method: string, path: string, body: any = null): Promise<T> {
      const hostUrl = process.env.PLANE_API_HOST_URL || "https://api.plane.so/";
      const host = hostUrl.endsWith("/") ? hostUrl : `${hostUrl}/`;
      const url = `${host}api/v1/${path}`;
      const headers: Record<string, string> = {
        "X-API-Key": process.env.PLANE_API_KEY || "",
      };
    
      // Only add Content-Type for non-GET requests
      if (method.toUpperCase() !== "GET") {
        headers["Content-Type"] = "application/json";
      }
    
      try {
        const config: AxiosRequestConfig = {
          url,
          method,
          headers,
        };
    
        // Only include body for non-GET requests
        if (method.toUpperCase() !== "GET" && body !== null) {
          config.data = body;
        }
    
        const response = await axios(config);
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Request failed: ${error.message}`);
        }
        throw error;
      }
    }
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 only states the basic action. It doesn't disclose behavioral traits like whether this is a read-only operation (implied by 'Get'), pagination, rate limits, authentication needs, or what 'all issues' entails (e.g., status filters). This leaves significant gaps for a tool with potential complexity.

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's front-loaded with the core action and resource, making it easy to parse quickly.

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 no annotations and no output schema, the description is minimally adequate but incomplete. It covers the basic purpose but lacks details on behavior, output format, or error handling, which are important for a tool that likely returns a list of issues.

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%, with clear parameter descriptions in the schema itself. The description adds no additional meaning beyond implying 'module_id' and 'project_id' are needed, which is already covered. Baseline 3 is appropriate as 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 'Get' and resource 'issues for a specific module', making the purpose understandable. It distinguishes from siblings like 'list_cycle_issues' by specifying 'module' scope, though it doesn't explicitly differentiate from 'get_issue_using_readable_identifier' or 'get_issue_comments' which have different purposes.

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 'get_issue_using_readable_identifier' (for single issues) or 'list_cycle_issues' (for cycle-specific issues). The description implies usage for module-related issues but lacks explicit context or exclusions.

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

Related 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/makeplane/plane-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server