Skip to main content
Glama

set_work_item_property_value

Idempotent

Set or update custom property values on work items, supporting text, dates, numbers, booleans, and option relations. Handles single and multi-value properties.

Instructions

Set (create or update) the value of a custom property on a work item.

Acts as an upsert - creates the value if it does not exist, updates it if it does. For multi-value properties (is_multi=True), replaces all existing values with the new ones.

Value types by property type: TEXT/URL/EMAIL/FILE: string DATETIME: string (YYYY-MM-DD or YYYY-MM-DD HH:MM:SS) DECIMAL: int or float BOOLEAN: true or false OPTION/RELATION (single): UUID string OPTION/RELATION (multi, is_multi=True): list of UUID strings

Args: project_id: UUID of the project work_item_id: UUID of the work item property_id: UUID of the work item property value: The value to set (type depends on the property type - see above) external_id: Optional external identifier for syncing external_source: Optional external source name (e.g. "github", "jira")

Returns: Single WorkItemPropertyValueDetail for non-multi properties, or list of WorkItemPropertyValueDetail for multi-value properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
project_idYes
external_idNo
property_idYes
work_item_idYes
external_sourceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations indicate mutation, idempotency, and non-destructiveness. Description adds important behavioral details: upsert semantics, multi-value replacement, and value type mappings. No contradictions with annotations.

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?

Description is well-structured, starting with a clear action sentence, then covering upsert behavior, value types, and parameters. Slightly verbose with the code block for types, but overall efficient and front-loaded.

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?

Given the tool's complexity (6 parameters, 4 required, output schema exists), the description covers all needed aspects: purpose, behavior, parameter details, and return type hint. It handles multi-value and type variations comprehensively.

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?

Schema description coverage is 0%, but the description compensates with detailed value type explanations for the 'value' parameter and lists all parameters with brief descriptions in the Args section. This adds significant meaning beyond the bare schema structure.

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 'Set (create or update) the value of a custom property on a work item' with specific verb and resource. It distinguishes from siblings like get_work_item_property_value and delete_work_item_property_value by specifying the upsert nature and value types for custom properties.

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 context on when to use the tool (creating or updating custom property values) and includes value type mappings. However, it does not explicitly mention when not to use it or point to alternative tools for reading or deleting property values, which would enhance guidance.

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