Skip to main content
Glama

manage_work_item_assignee

Manage work item assignees by adding or removing a single user without affecting other assignees.

Instructions

Add or remove a single assignee on a work item without replacing the full list.

Provide add_user_id, remove_user_id, or both. If both are given the removal is applied first, then the addition. Already-assigned users in add_user_id are silently skipped.

Args: project_id: UUID of the project work_item_id: UUID of the work item add_user_id: UUID of the user to add as assignee remove_user_id: UUID of the user to remove from assignees

Returns: Updated WorkItem object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
add_user_idNo
work_item_idYes
remove_user_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
typeNo
pointNo
stateNo
parentNo
projectNo
type_idNo
is_draftNo
priorityNo
workspaceNo
created_atNo
created_byNo
deleted_atNo
sort_orderNo
start_dateNo
updated_atNo
updated_byNo
archived_atNo
external_idNo
sequence_idNo
target_dateNo
completed_atNo
estimate_pointNo
external_sourceNo
description_htmlNo
description_binaryNo
description_strippedNo
Behavior5/5

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

Discloses behavioral traits: removal applied first, silent skip for already-assigned users, and no full list replacement. Beyond annotations (readOnlyHint=false, openWorldHint=true), it clarifies side effects.

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?

Efficiently structured: summary sentence, then parameter list, behavior notes, and return value. No unnecessary words, front-loaded with key action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete given complexity: mutation tool with output schema noted, parameter semantics covered, behavioral nuances explained, and no missing context for selection among siblings.

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

Parameters5/5

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

Adds full meaning for each parameter (UUID types), explains optionality and defaults, and describes combined usage. Schema has no descriptions, so description fully compensates.

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 tool adds or removes a single assignee without replacing the full list, distinguishing it from sibling tools like update_work_item that might modify other aspects.

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?

Provides clear instructions on providing parameters and order of operations (removal before addition). Lacks explicit alternatives for full list replacement, but context is adequate.

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/Bl4nk44/plane-ce-mcp'

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