Skip to main content
Glama
Sign In

Milanote MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Move card

move_card
Destructive

Move a card or a sub-board to another board, or into or out of a column. Moves it the way drag and drop does, keeping its ID, comments and content. With to_column_id it goes to the top of that column; without it, to the top of the target board's Unsorted panel. Moving a board moves everything inside it. Moving to a board shared with other people shows it to them.

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": {
      "board_id": "<board_id>",
      "card_id": "<card_id>"
    },
    "name": "move_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYesCard ID from get_board; a sub-board's board_id works too.
board_idYesBoard the card is on now: ID or board URL.
to_board_idNoBoard to move it to. Default: the same board.
to_column_idNoColumn on the target board to put it in, at the top. Default: no column.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds real context beyond the annotations: the move preserves card ID, comments, and content; it behaves like drag-and-drop; moving a sub-board moves its contents; and the move becomes visible to others on a shared board. This complements destructiveHint=true and idempotentHint=false, though it doesn't address reversibility or permission requirements for cross-board moves.

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?

Four short sentences, each carrying distinct information: scope, preserved state, placement defaults, sub-board semantics, and visibility side effects. Nothing is redundant and the core verb leads.

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 destructive, non-idempotent mutation with no output schema, the description covers placement, preservation, recursion into sub-boards, and shared-board visibility. Remaining gaps are error behavior and permission prerequisites for cross-board moves, which are minor given 100% schema coverage and the annotation safety profile.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning not in the schema: the resulting placement when to_column_id is supplied (top of column) versus omitted (Unsorted panel). It also implicitly clarifies that omitting to_board_id is a same-board reorder within or out of a column.

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?

States a specific verb and resource ('Move a card or a sub-board') plus the destinations it supports (another board, into/out of a column). It is clearly distinguishable from siblings like trash_cards, restore_card, and add_column, which are different operations.

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?

Explicitly covers the branching behavior of to_column_id (top of that column) versus omitting it (top of the target board's Unsorted panel), and notes to_board_id defaults to the same board. It does not name alternative tools or contrast with trash_cards/restore_card for cards that should be removed rather than moved.

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

All Milanote MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources