Skip to main content
Glama
MakarGlavanar

WEEEK MCP Server

weeek_move_task

Move a WEEEK task to a different board column to change its status. Requires task ID and destination column ID.

Instructions

Move a WEEEK task to a different board column. This IS how you change a task's status in WEEEK — columns ARE the status mechanism. WRITE OPERATION — the MCP client may prompt for confirmation. Required: task_id and board_column_id. Optional: board_id (only when moving across boards), mr_url (records a merge/pull request link on the "МР" custom field in the same call), field_name (only with mr_url). Returns the updated task. DISTINCT from weeek_update_task: use update for field edits (title, description, priority, assignee, due date); use move for column/status changes. DISTINCT from weeek_complete_task: use complete for the done/undone toggle even though 'completed' is visually similar to a 'Done' column. board_column_id must come from weeek_list_board_columns — do not guess.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mr_urlNoMerge/pull request URL to record on the task's "МР" custom field in the same call as the status change. Optional. Omit to leave the field unchanged. Use weeek_set_task_mr_link instead if there is no status change happening.
task_idYesWEEEK task ID to move. Required. Obtain from weeek_list_tasks.
board_idNoDestination board ID. Optional — only needed when moving the task to a column on a DIFFERENT board than its current one.
field_nameNoName of the custom field to write mr_url into. Optional — defaults to "МР". Only used when mr_url is provided.
board_column_idYesDestination column ID. Required. Obtain from weeek_list_board_columns. Moving a task to a new column IS the status change in WEEEK.
Behavior4/5

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

No annotations provided, so description carries full burden. It labels itself as a WRITE OPERATION with possible confirmation prompt, describes effect (status change, optional MR link), and notes board_id usage. Some minor behavioral details (reversibility, notifications) omitted, but overall transparent.

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?

Description is somewhat lengthy but every sentence contributes value. Front-loaded with core purpose. Could combine some points for slightly tighter prose, but still well-structured.

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?

No output schema, but description notes it returns updated task. All 5 parameters covered, required ones emphasized, sibling distinctions provided. Complete for the tool's complexity and context.

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

Parameters5/5

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

Schema description coverage is 100%, but description adds key context: board_column_id is the destination column, moving equals status change, warns against guessing column IDs, explains mr_url and field_name relationship, and clarifies board_id optionality across boards.

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 the verb 'Move' and resource 'task to a different board column', immediately distinguishing it from update and complete tools. It avoids tautology and is specific.

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 to use this tool (changing column/status) and when not (use update for field edits, complete for done/undone, set_mr_link without status change). Also specifies prerequisite: get board_column_id from weeek_list_board_columns.

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/MakarGlavanar/weeek-mcp'

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