Skip to main content
Glama

karea_edit_task

Edit an existing task by updating its title, priority, status, deadline, description, markdown, category, notes, tags, closing requisites, JIRA link, or project.

Instructions

Edit an existing task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesTask name, visual ID (C1, T2), or UUID
nameNoNew task title (rename the task)
priorityNoNew priority
statusNoNew status: open, in_progress, blocked, review, done
slaNoNew deadline
descriptionNoNew description (short, one line)
markdownNoLong-form markdown content — use for investigation findings, technical/functional docs, solution design, root cause analysis. Overwrites existing markdown; read first with karea_get_markdown to append.
categoryNoMove to category
noteNoAdd a note
tagsNoTags to add (e.g. ["bug", "needs review"])
clearTagsNoRemove all existing tags before adding new ones
closingRequisitesNoClosing requisites to add
clearClosingRequisitesNoRemove all existing closing requisites before adding new ones
jiraIssueKeyNoJIRA issue key to link (e.g. PROJ-123). Set to "unlink" to remove.
projectIdNoProject name or ID
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'edit' without disclosing side effects (e.g., markdown overwrites existing content, tags can be cleared). Lacks behavioral traits like idempotency or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise (one sentence) but at the expense of missing important details. Front-loaded but under-specified for a complex tool.

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?

For a tool with 15 parameters and no output schema, the description is too minimal. It does not explain common use cases, parameter interactions, or typical workflows.

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 baseline is 3. The description adds no additional parameter meaning beyond what the schema already provides.

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?

Description states verb 'Edit' and resource 'existing task', which is clear. However, it does not differentiate from sibling tools like karea_set_markdown or karea_close_task that could be used to edit specific aspects.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like karea_set_markdown for markdown or karea_add_note for notes. No exclusions or context provided.

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/starecz/karea-mcp'

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