Skip to main content
Glama

move_card

Change a card's workflow status by moving it to a different list in Trello, such as from "To Do" to "In Progress".

Instructions

Move a card to a different list. Use this to change a card's workflow status (e.g., from "To Do" to "In Progress").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesTrello API key (automatically provided by Claude.app from your stored credentials)
tokenYesTrello API token (automatically provided by Claude.app from your stored credentials)
cardIdYesID of the card to move (you can get this from board details or card searches)
idListYesID of the destination list (you can get this from get_lists)
posNoPosition in the destination list: "top", "bottom", or specific number

Implementation Reference

  • The handler function for the 'move_card' tool, which validates input and calls the Trello API client.
    export async function handleMoveCard(args: unknown) {
      try {
        const moveData = validateMoveCard(args);
        const { apiKey, token, cardId, ...moveParams } = moveData;
        
        const client = new TrelloClient({ apiKey, token });
        const response = await client.moveCard(cardId, moveParams);
        const card = response.data;
        
        const result = {
          summary: `Moved card "${card.name}" to list ${card.idList}`,
          card: {
            id: card.id,
            name: card.name,
            url: card.shortUrl,
            listId: card.idList,
            boardId: card.idBoard,
            position: card.pos
          },
          rateLimit: response.rateLimit
        };
        
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof z.ZodError 
          ? formatValidationError(error)
          : error instanceof Error 
            ? error.message 
            : 'Unknown error occurred';
            
        return {
          content: [
            {
              type: 'text' as const,
              text: `Error moving card: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • The tool definition and input schema for the 'move_card' tool.
    export const moveCardTool: Tool = {
      name: 'move_card',
      description: 'Move a card to a different list. Use this to change a card\'s workflow status (e.g., from "To Do" to "In Progress").',
      inputSchema: {
        type: 'object',
        properties: {
          apiKey: {
            type: 'string',
            description: 'Trello API key (automatically provided by Claude.app from your stored credentials)'
          },
          token: {
            type: 'string',
            description: 'Trello API token (automatically provided by Claude.app from your stored credentials)'
          },
          cardId: {
            type: 'string',
            description: 'ID of the card to move (you can get this from board details or card searches)',
            pattern: '^[a-f0-9]{24}$'
          },
          idList: {
            type: 'string',
            description: 'ID of the destination list (you can get this from get_lists)',
            pattern: '^[a-f0-9]{24}$'
          },
          pos: {
            oneOf: [
              { type: 'number', minimum: 0 },
              { type: 'string', enum: ['top', 'bottom'] }
            ],
            description: 'Position in the destination list: "top", "bottom", or specific number'
          }
        },
        required: ['apiKey', 'token', 'cardId', 'idList']
      }
    };
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It lacks details on permissions needed, rate limits, error conditions, or what happens to card data during the move, which are important for a mutation tool.

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?

Two concise sentences with zero waste: the first states the core action, the second provides usage context. It is front-loaded and efficiently structured.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description is minimal but adequate. It covers purpose and basic usage but lacks behavioral details like error handling or return values, leaving gaps in completeness.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional parameter semantics beyond implying 'idList' relates to workflow status, meeting the baseline for high schema coverage.

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 specific action ('Move a card') and resource ('to a different list'), with an explicit example distinguishing it from siblings like 'update_card' or 'create_card' by focusing on workflow status changes.

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 provides clear context for when to use this tool ('to change a card's workflow status'), but does not explicitly mention when not to use it or name alternatives like 'update_card' for other modifications.

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/kocakli/Trello-Desktop-MCP'

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