Skip to main content
Glama

update_standard_work_item

Update a Plane work item while preserving labels and description unless a structured replacement is requested; preview changes with a dry run before applying.

Instructions

Preview or update a specific Plane work item while preserving labels and description unless a structured replacement is requested.

Input Schema

NameRequiredDescriptionDefault
scopeNo
contextNo
dry_runNo
outcomeNo
surfaceNo
cycle_idNo
estimateNo
priorityNo
state_idNo
project_idNo
release_idNo
start_dateNo
module_nameNo
target_dateNo
title_partsNo
assignee_idsNo
work_item_idYes
work_item_typeNo
current_behaviorNo
additional_labelsNo
expected_behaviorNo
module_descriptionNo
acceptance_criteriaNo
allow_create_moduleNo
replace_descriptionNo
confirm_project_identifierNoOnly to target a project other than the active one: the target project's identifier (for example WEB). The call is rejected unless it matches project_id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

C2.9/5.0
Behavior3/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 usefully discloses preview/update behavior and default preservation of labels and description unless structured replacement is requested, but it omits permissions, partial-update semantics, side effects, null handling, and what preview returns.

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

Conciseness4/5

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

The single sentence is front-loaded with the main action and contains no filler. It is concise, though its brevity leaves no structured guidance for a tool with 26 parameters.

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 26 parameters, 4% schema description coverage, and no annotations, the one-sentence description is not complete enough. The output schema exists so return values needn't be described, but usage and parameter guidance are substantially missing.

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

Parameters2/5

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

Schema description coverage is only 4% across 26 parameters. The description hints at dry_run, replace_description, and labels/description preservation, but it leaves nearly all parameters undocumented and does not compensate for the low schema coverage.

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 states a specific verb and resource: 'Preview or update a specific Plane work item.' It is clear what the tool acts on, but it does not distinguish this from sibling tools such as create_standard_work_item, start_standard_work_item, or complete_standard_work_item.

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?

It implies preview mode through 'Preview or update' and mentions preservation unless a structured replacement is requested, but gives no explicit when-to-use guidance. It does not say when to choose preview versus update, nor when to use this instead of create/start/complete/cancel siblings.

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