Skip to main content
Glama

archive_task

DestructiveIdempotent

Archive a task in Kanban Tool by task ID. Returns updated task with is_archived=True, idempotent for already-archived tasks.

Instructions

Archive a task. Returns the updated Task (caller can confirm is_archived=True).

Idempotent: re-archiving an already-archived task succeeds. There is no unarchive_task yet — archiving is currently one-way from this surface.

Failure modes: KanbanToolHTTPError(404) when the task id is unknown (verify via get_task(task_id) first if you're unsure); KanbanToolPermissionError(403) when the authenticated user lacks write access to the task's board.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
descriptionNo
board_idNo
workflow_stage_idNo
swimlane_idNo
positionNo
priorityNo
colorNo
due_dateNo
start_dateNo
tagsNo
assigned_user_idNo
archived_atNo
block_reasonNo
subtasks_countNo
subtasksNo
comments_countNo
timers_totalNo
time_trackersNo
created_atNo
updated_atNo
size_estimateNo
size_estimate_descriptionNo
time_estimateNo
search_tagsNo
card_colorNo
card_color_in_rgbNo
card_color_invertNo
card_type_idNo
recurring_scheduleNo
reminders_scheduleNo
linked_tasksNo
linked_tasks_statusNo
task_dependenciesNo
collaboratorsNo
attachmentsNo
attachments_countNo
created_by_idNo
moved_atNo
postponed_untilNo
subtasks_completed_countNo
external_idNo
external_linkNo
custom_fieldsNo
is_archivedYesTrue iff the task has an archival timestamp.
is_blockedYesTrue iff the task has a non-empty block reason.
Behavior5/5

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

The description expands on annotations: idempotency is explained in detail ('re-archiving an already-archived task succeeds'), destructiveHint is supported by the one-way nature, and failure modes (404, 403) are listed. No contradiction with annotations.

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 three short paragraphs: purpose, idempotency/irreversibility, failure modes. Each sentence adds value, and the key information is front-loaded.

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 one parameter and no output schema (but description mentions return value), the description covers purpose, idempotency, irreversibility, failure modes, and a suggested pre-check. No gaps remain.

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?

The only parameter task_id has no schema description (0% coverage). The description adds minimal guidance by referencing task id verification via get_task, but does not describe the parameter format or constraints beyond what schema provides. For a simple integer parameter, a baseline of 3 is appropriate.

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 'Archive a task' as the verb+resource, and explains the effect (returns updated Task with is_archived=True). Among sibling tools, no other archive tool exists, so it is fully distinguishable.

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 warns that 'archiving is currently one-way from this surface' and suggests verifying the task id with get_task first. This gives clear guidance on when to use and what precautions to take.

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/VeryLongOrgNameSuchWow/kanbantool-mcp'

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