Plane MCP

add_work_items_to_module

Add one or more work items to a module by specifying module ID and issue UUIDs. Organize related issues within Plane modules.

Instructions

Add one or more work items (by UUID) to a module.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "module_id": "<module_id>",
      "issue_ids": "<issue_ids>"
    },
    "name": "add_work_items_to_module"
  }
}

Input Schema

Name	Required	Description	Default
`issue_ids`	Yes
`module_id`	Yes
`project_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description alone must disclose behavioral traits. It only states the action and the identifier format (UUID). It does not mention idempotency, handling of duplicate items, effects on existing associations, permissions, or the role of the optional project_id. This is a significant gap for a mutating tool.

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, clear sentence with no extraneous details. It is front-loaded with the action and resource, and every word contributes to understanding. This is ideal conciseness.

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 mutation nature, three parameters, and close sibling relationships, the description is too sparse. It lacks operational context such as whether the module must already exist, what happens when adding duplicates, and how project_id relates. The output schema exists but does not offset the absence of these behavioral and parameter details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no parameter descriptions (0% coverage), and the description only clarifies that work items are identified by UUID. It does not explain the meaning or purpose of module_id, issue_ids (beyond being an array), or project_id. The description fails to compensate for the missing schema documentation.

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 a specific verb ('Add') and clearly identifies the resource ('work items to a module') and the identifier type (UUID). It effectively distinguishes the tool from sibling operations like add_work_items_to_cycle and remove_work_item_from_module.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies the intended use case: when a user needs to associate work items with a module. It does not explicitly mention alternatives or exclusions, but the context from the tool name and sibling tools makes the usage clear. There is no misleading guidance, so it earns a 4.

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