Skip to main content
Glama
makeplane

Plane MCP Server

Official
by makeplane

add_module_issues

Assign issues to a module in a project. Use this tool to link specific issue UUIDs to a module, ensuring organized task management within Plane MCP Server.

Instructions

Add issues to a module. Assign module to issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issuesYesArray of issue UUIDs to add to the module
module_idYesThe uuid identifier of the module to add issues to
project_idYesThe uuid identifier of the project containing the module

Implementation Reference

  • The main handler function that performs the POST request to the Plane API endpoint to associate issues with a module.
    async ({ project_id, module_id, issues }) => {
      const response = await makePlaneRequest(
        "POST",
        `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/modules/${module_id}/module-issues/`,
        { issues }
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • Input schema using Zod validators for the tool 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 add issues to"),
      issues: z.array(z.string()).describe("Array of issue UUIDs to add to the module"),
    },
  • MCP server tool registration call, specifying name, description, input schema, and handler function.
    server.tool(
      "add_module_issues",
      "Add issues to a module. Assign module to issues.",
      {
        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 add issues to"),
        issues: z.array(z.string()).describe("Array of issue UUIDs to add to the module"),
      },
      async ({ project_id, module_id, issues }) => {
        const response = await makePlaneRequest(
          "POST",
          `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/modules/${module_id}/module-issues/`,
          { issues }
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      }
    );
  • Call to register module issue tools (including add_module_issues) within the aggregate tools registration.
    registerModuleIssueTools(server);
  • src/server.ts:15-15 (registration)
    Top-level call to register all tools, which chains to module-issues tools.
    registerTools(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool 'adds' and 'assigns', implying a mutation, but lacks critical behavioral details: it does not specify permissions required, whether issues can be added multiple times, error handling (e.g., invalid UUIDs), or the effect on existing module-issue relationships. This is inadequate for a mutation tool with zero annotation coverage.

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 with two short sentences that directly state the tool's purpose. It is front-loaded and wastes no words, making it easy to parse quickly without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context (e.g., side effects, error cases), usage guidelines, and details on return values. While the schema covers parameters well, the overall context for safe and effective use is insufficient, especially given the complexity of modifying data relationships.

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 (e.g., 'Array of issue UUIDs'). The description adds no additional meaning beyond the schema, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 action ('Add issues to a module') and the resource ('module'), which is specific and actionable. It distinguishes from siblings like 'delete_module_issue' or 'list_module_issues' by focusing on addition, but does not explicitly differentiate from similar tools like 'add_cycle_issues' beyond the resource name.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., existing module/issues), exclusions, or compare to siblings like 'add_cycle_issues' or 'create_issue', leaving the agent to infer usage from context alone.

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