Skip to main content
Glama
outputty

tasks-mcp

by outputty
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

edit_task

Edit any field of a task—title, brief, contract, deps, scope, tier, QA, priority, spec, stage, kind, tags, target, type—without changing its ID. Only passed fields change; clearing removes labels.

Instructions

Edit any field of a task — title, brief, contract, deps, scope, tier, qa, priority, spec, stage, kind, tags, target, type. Only the fields passed change; the id is fixed. Rewrites the issue body and labels. Unlike amend_task, it can narrow scope and edit a done task.

To REMOVE a field rather than change it, name it in clear — that is the only way a field:value label comes off an issue without opening the GitHub UI. Setting a field back to its default (tier 3, qa subagent, priority normal, spec settled) also drops its label, since absence already means the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe task id (unchanged).
qaNoHow much review.
depsNoIds this task waits on (REPLACES the list).
kindNoFree-text classifier — feature | bug | chore | yours.
specNoPlanning lifecycle.
tagsNoFree-form GitHub labels, verbatim and with no `field:` prefix (`frontend`, `security`). REPLACES the list. Adopted from the issue on every pull, so a label added in the web UI flows back.
tierNo1-4; how much model the work needs.
typeNotask | target. Promoting to target demands a title and a brief, and refuses build fields — clear scope/contract/tier/qa/stage first.
briefNoThe build brief: the problem and expected solution.
clearNoFields to REMOVE outright — the only way a label comes off an issue. Clearing a list empties it. One of: type, target, kind, brief, contract, tier, qa, priority, spec, stage, discovered_from, deps, scope, tags.
scopeNoFolders the task may edit (REPLACES the list).
stageNoNarrative label on a staged deliverable.
titleNoOne-line summary.
branchNoBranch to scope to (optional; the backend decides its use).
targetNoMove this under a different roadmap target (re-parents its issue).
projectNoThe project id — an opaque, supplied string, never derived. Omit to use the server's --project-id default.
contractNoThe done-condition (what to account for).
priorityNoHow urgent.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.21.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full disclosure burden, and it does so thoroughly. It states that only passed fields change, that the id is fixed, and that the operation rewrites the issue body and labels. It also reveals the non-obvious label-removal mechanics around clear and default values, which are exactly the behavioral details an agent needs.

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?

The description is focused and front-loaded: purpose first, then key constraints, then a separate paragraph for the non-obvious clear behavior. Every sentence contributes necessary operational detail without padding.

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 — 18 parameters, label side effects, and a sibling with overlapping purpose — the description is complete enough for correct invocation. Hidden behaviors like label rewriting, default-drops-label, and clear-only removal are all covered, and the rich schema handles parameter-level details.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds value by explaining that only provided fields are modified and by clarifying the clear parameter's label-removal semantics, which go beyond individual schema descriptions.

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 opens with a specific verb and resource: 'Edit any field of a task,' followed by the full field list. It further distinguishes itself from amend_task by noting it 'can narrow scope and edit a done task,' making its purpose and boundaries immediately clear.

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?

The description explicitly contrasts with amend_task, telling the agent when edit_task is the right choice. It also explains when to use the clear parameter for removing fields versus simply setting new values. It could be more explicit about when not to use the tool, but the named sibling comparison provides strong 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/outputty/tasks-mcp'

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