Skip to main content
Glama

Edit task description

edit_task_content
Destructive

Apply targeted Markdown edits to a task after reading its current content. Prefer exact text or block edits; preserve unrelated content. Full rewrites and large removals are checked by the collaborative editor. Set allowRemoval only for a user-requested removal. Re-read after a conflict; never blindly retry. Preserve requestId on retries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "requestId": "<requestId>",
      "id": "<id>",
      "edits": "<edits>"
    },
    "name": "edit_task_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExisting target ID returned by the matching list, read or search tool. Preserve any search type prefix. Do not invent IDs.
editsYes1–20 targeted edits, at most 50,000 characters total.
requestIdYesA unique UUID for this intended action. Reuse it unchanged when retrying the same action.
allowRemovalNoTrue only when the user explicitly requested the removal of existing content.

Output Schema

NameRequiredDescriptionDefault
editYesEdworking record fields permitted for this connection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Well beyond what the annotations declare: it explains that full rewrites and large removals are checked by the collaborative editor, how conflicts should be handled (re-read, don't blindly retry), and the retry/idempotency contract for requestId. These are exactly the behaviors an agent needs and none are present in the structured fields.

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?

Front-loaded with the core action in the first sentence, then the editing preference, then the safety and retry rules. The telegraphic style is dense but every sentence carries a distinct constraint; nothing is padding.

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?

With rich annotations, an output schema, and full schema coverage, the description only needs to carry the behavioral contract — conflict handling, retry semantics, and removal restrictions — which it does. The individual edit actions are left to the schema, which is reasonable for a 4-parameter tool.

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 description coverage is 100%, so the schema already documents all four parameters including allowRemoval and requestId. The description largely restates those constraints (allowRemoval for user-requested removals, preserve requestId on retries) rather than adding new semantics, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource: targeted Markdown edits to a task's description, with the implicit prerequisite of reading the current content. It's clearly distinct from the doc-editing sibling because it scopes to a task, though it never names an alternative tool explicitly.

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?

Strong operational guidance: prefer exact text or block edits, preserve unrelated content, set allowRemoval only for user-requested removals, re-read after conflict, and never blindly retry. It gives clear conditions and a negative rule (allowRemoval), but stops short of explicitly routing the agent away from full rewrites toward a different tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.