Skip to main content
Glama

backlog_update

Update an existing task's status, title, parent, or schedule. Supports blocking reasons, completion evidence, and cron configuration.

Instructions

Update an existing item. For editing the markdown body, use write_resource with str_replace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask ID to update
titleNoNew title
statusNoNew status
epic_idNoParent epic ID (null to unlink)
parent_idNoParent ID (null to unlink). Takes precedence over epic_id.
blocked_reasonNoReason if status is blocked
evidenceNoProof of completion when marking done - links to PRs, docs, or notes
referencesNoReference links. Formats: external URLs (https://...), task refs (mcp://backlog/tasks/TASK-XXXX.md), resources (mcp://backlog/resources/{path}). Local files must include extension (file:///path/to/file.md)
due_dateNoDue date for milestones (ISO 8601). Null to clear.
content_typeNoContent type for artifacts (e.g. text/markdown). Null to clear.
scheduleNoCron expression (5 fields). Validated on write. Only permitted on cron entities.
commandNoCommand string for external scheduler. Only permitted on cron entities.
enabledNoWhether the external scheduler should tick this cron. Separate from status. Only permitted on cron entities.
last_runNoISO-8601 timestamp of most recent scheduler tick. Typically written by the scheduler. Null to clear (e.g. scheduler reset).
next_runNoISO-8601 timestamp of next scheduled tick. Typically written by the scheduler. Null to clear.
Behavior2/5

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

No annotations provided; description implies mutation but lacks details on side effects, auth, or error states.

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?

Single sentence, no wasted words.

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?

15-parameter tool with no output schema and minimal description; lacks return value or success/failure info.

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 covers all parameters (100%), description adds no additional meaning beyond schema.

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 'Update an existing item' and differentiates from write_resource for markdown body editing.

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 explicit guidance to use write_resource for markdown body instead, but no other when/when-not context.

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/gkoreli/backlog-mcp'

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