Skip to main content
Glama

Reorder a list

kanbini_move_list

Move a kanban list to a new position on its board by specifying a left or right neighbour; omit both to place it at the far right.

Instructions

Move a list (column) to a new position on its board. Named from the moved list's point of view: beforeId is the list that will sit directly to its LEFT, afterId the list directly to its RIGHT. So to put list X just right of list Y, pass beforeId: Y. One neighbour is enough, the server works out the other. Omit both for the far right; pass only afterId = the first list for the far left. Neighbours must be lists on the same board (closed lists count too, since they keep their slot). A list can be given by its id, or by its exact name with boardId.

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": {
      "id": "<id>"
    },
    "name": "kanbini_move_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
afterIdNoList that will sit directly RIGHT of the moved list
boardIdNoThe board's id or exact name. Needed when you name a card by number (#142) or a list / label by name.
beforeIdNoList that will sit directly LEFT of the moved list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.0
    • addedInput schema / properties / boardId
      Added value: +{
      +  "description": "The board's id or exact name. Needed when you name a card by number (#142) or a list / label by name.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv0.15.0
    • addedInput schema / properties / afterId / description
      Added value: +"List that will sit directly RIGHT of the moved list"
    • addedInput schema / properties / beforeId / description
      Added value: +"List that will sit directly LEFT of the moved list"
  3. First observedv0.13.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses useful behavior: neighbour resolution, same-board constraints, closed-list inclusion, and name-based lookup. It does not cover permissions, reversibility, error behavior, or what the operation returns, which leaves some mutation-related gaps.

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 front-loaded and well organized: it states the operation, explains the directional naming convention, gives example usage, then covers edge cases and naming. Every sentence contributes to correct invocation, with no visible 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?

For a four-parameter reorder operation with no output schema and no annotations, the description covers nearly everything needed to position a list correctly. It could be more complete by stating the response shape or error behavior for invalid neighbours.

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?

The description adds substantial meaning beyond the schema, including the moved-list point of view, a concrete `beforeId` example, edge cases for omission, same-board neighbour rules, closed-list behavior, and id/name resolution with `boardId`. This significantly clarifies the four parameters even though schema coverage is already 75%.

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 opens with a specific verb and resource: 'Move a list (column) to a new position on its board.' That clearly distinguishes a list reorder from sibling operations such as moving cards or updating list metadata.

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?

It explains how to use the tool for different target positions, including omitting both neighbours for far right and passing only `afterId` for far left. It does not explicitly compare against alternatives like `kanbini_move_card` or `kanbini_update_list`, but the positional semantics make the intended use clear.

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