Wekan MCP Server

moveCard

Move a card to a different list or swimlane within a board by specifying the board, card, and target list.

Instructions

Move a card to another list or swimlane

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": {
      "boardId": "<boardId>",
      "cardId": "<cardId>"
    },
    "name": "moveCard"
  }
}

Input Schema

Name	Required	Description	Default
`boardId`	Yes
`cardId`	Yes
`listId`	No
`swimlaneId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 7, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations provided; description only states the basic action. Does not disclose potential errors, side effects (e.g., what happens if card already in target list), or required permissions for mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no wasted words. However, it is under-specified for the number of parameters and lack of other documentation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description is too brief given the lack of annotations and output schema. Missing details on required parameters, typical usage patterns, and error handling. Incomplete for a mutation tool.

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

Parameters2/5

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

Schema coverage is 0%, and description only mentions list and swimlane implicitly. Does not clarify the role of boardId and cardId, nor which parameters are optional. Adds minimal value beyond the parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the action (move) and resource (card), and implies the target (list or swimlane), distinguishing it from sibling tools like createCard or listCards. However, it could be more explicit about the scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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 when a card needs to be reorganized within a board. No prerequisites or exclusions mentioned.

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

Deploy Server