Skip to main content
Glama
backloghq

backlog

Modify Task

task_modify

Update one or multiple tasks by filter criteria. Modify descriptions, projects, priorities, dates, tags, dependencies, or assignments using partial updates—only specified fields change while existing values remain untouched.

Instructions

Update one or more tasks matching a filter. Only provided fields are changed — omitted fields are left untouched (partial update). The filter can match multiple tasks; all matches are updated with the same changes. Returns the count of modified tasks. Use task_done/task_delete/task_start/task_stop for status changes instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterYesFilter to select tasks. Can be a numeric ID ('1'), UUID, or filter expression ('project:backend priority:H'). Matches may update multiple tasks.
descriptionNoNew description text (max 500 chars). Only set if you want to change it.
projectNoNew project name. Pass empty string to clear.
tagsNoTags to add (+) or remove (-). E.g. '+frontend,+urgent' or '-old,+new'. Prefix with + to add, - to remove. Without prefix, tags are added.
priorityNoNew priority. Pass empty string to clear priority entirely.
dueNoNew due date. Accepts ISO dates, relative ('3d'), named ('friday', 'eow'). Pass empty string to clear.
dependsNoNew dependency UUIDs (comma-separated). Replaces existing dependencies. Pass empty string to clear.
waitNoNew wait date. Task hidden from default views until this date. Pass empty string to clear.
scheduledNoNew scheduled start date. Pass empty string to clear.
recurNoNew recurrence pattern ('daily', 'weekly', '3d', etc). Pass empty string to clear.
untilNoEnd date for recurrence. Pass empty string to clear.
agentNoAgent identity. Pass empty string to unassign.
extraNoSpace-separated additional attributes or +tag/-tag modifiers.
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses partial update semantics (omitted fields untouched), bulk behavior (filter matches multiple), and return value (count). Lacks mention of zero-match behavior or permissions, but covers primary mutation concerns well.

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?

Five sentences, zero waste. Front-loaded with core purpose, followed by behavioral semantics, return value, and sibling alternatives. Every sentence earns its place with dense, actionable information.

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

Completeness4/5

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

Adequately complete for a 13-parameter mutation tool. Explains return value (filling gap of missing output schema), partial updates, and bulk matching. Could mention edge cases like zero matches or permissions, but covers essential complexity given rich input schema.

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 has 100% description coverage, establishing baseline 3. Description adds valuable usage context about partial updates and bulk operations, but does not need to supplement individual parameter documentation since schema is comprehensive.

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?

Excellent specificity with verb 'Update', resource 'tasks', and scope 'one or more'. Explicitly distinguishes from siblings by naming task_done/task_delete/task_start/task_stop as alternatives for status changes, preventing incorrect usage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when NOT to use the tool ('Use task_done/task_delete/task_start/task_stop for status changes instead'). Also clarifies bulk update semantics and partial update behavior, giving clear guidance on tool selection and operation.

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/backloghq/backlog'

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