Reorder columns on a board by moving a column to a new position. Specify column ID or name and target index to change workflow order.
Move a column to a new position.
| Name | Required | Description | Default |
|---|---|---|---|
| board | No | Board ID or name (required for name lookup) | |
| column | Yes | Column ID or name | |
| position | Yes | New position index (0-based) |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.2Input schema / additionalPropertiesAdded value: +falseInput schema / properties / board / descriptionAdded value: +"Board ID or name (required for name lookup)"Input schema / properties / column / descriptionAdded value: +"Column ID or name"Input schema / properties / position / descriptionAdded value: +"New position index (0-based)"v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description does not disclose side effects, such as impact on column ordering of other columns or potential data loss. No mention of required permissions or immediate effect.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no extraneous words. Information is front-loaded and clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema, the description fails to explain what happens to other columns during a move, or that the move is within the same board. Lacks completeness for a mutation operation with potential side effects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema already describes parameters with 100% coverage. Description adds no additional meaning beyond what is in the schema, such as implications of moving on column indices or valid position ranges.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action 'move a column to a new position', which distinguishes it from siblings like rename_column or delete_column. It uses a specific verb and resource with clear scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives, such as move_card or list_columns. No prerequisites or context are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.