Skip to main content
Glama
goto-software

plane-mcp-server

update_module

Update a project module's details by providing its ID and the fields to change.

Instructions

Update a module by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
module_idYesUUID of the module
nameNoModule name
descriptionNoModule description
start_dateNoModule start date (ISO 8601 format)
target_dateNoModule target/end date (ISO 8601 format)
statusNoModule status (backlog, planned, in-progress, paused, completed, cancelled)
leadNoUUID of the user who leads the module
membersNoList of user IDs who are members of the module
external_sourceNoExternal system source name
external_idNoExternal system identifier

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
total_issuesNo
cancelled_issuesNo
completed_issuesNo
started_issuesNo
unstarted_issuesNo
backlog_issuesNo
created_atNo
updated_atNo
deleted_atNo
nameYes
descriptionNo
description_textNo
description_htmlNo
start_dateNo
target_dateNo
statusNo
view_propsNo
sort_orderNo
external_sourceNo
external_idNo
archived_atNo
logo_propsNo
created_byNo
updated_byNo
projectNo
workspaceNo
leadNo
Behavior1/5

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

No annotations exist, so the description must disclose behavioral traits. It only states 'Update a module by ID' without explaining partial update behavior, error handling, permissions, or idempotency. This is a severe deficiency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence) but omits critical details, making it inefficient for an agent. It is front-loaded but lacks substance.

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 (11 parameters), lack of annotations, and presence of an output schema, the description should cover update behavior, required fields, and typical use cases. It fails to provide sufficient context.

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 already documents each parameter. The description adds no additional meaning, but the baseline is met.

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 clearly states the verb 'Update', the resource 'module', and the method 'by ID', which distinguishes it from siblings like create_module, archive_module, delete_module.

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 is provided on when to use this tool versus alternatives (e.g., creating a new module, archiving, or deleting). There are no contextual hints about prerequisites or scenarios.

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/goto-software/plane-mcp-server'

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