Skip to main content
Glama

move-card

Move Trello cards between lists or reposition them within a list using card and destination list IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardIdYesID of the card to move
listIdYesID of the destination list
positionNoPosition in the list (e.g. "top", "bottom")

Implementation Reference

  • Input schema and description for the 'move_card_to_list' tool (exact match for move-card functionality).
    name: "move_card_to_list",
    description: "Move a card to a different list. Use this tool to change the status of a card.",
    inputSchema: {
        type: "object",
        properties: {
            cardId: {
                type: "string",
                description: "ID of the card to move"
            },
            listId: {
                type: "string",
                description: "ID of the destination list"
            }
        },
        required: ["cardId", "listId"]
    }
  • The tool handler function that executes the logic for moving a card to a new list by calling the CardService.
    move_card_to_list: async (args: any) => {
        const cardService = ServiceFactory.getInstance().getCardService();
        return cardService.moveCardToList(args.cardId, args.listId);
    },
  • src/index.ts:97-101 (registration)
    MCP server registration for listing all tools, including 'move_card_to_list' via the trelloTools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
        return {
            tools: trelloTools
        };
    });
  • src/index.ts:125-169 (registration)
    MCP server registration for calling tools; dispatches to specific tool handler like move_card_to_list using trelloToolHandlers.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
        try {
            const toolName = request.params.name;
            // Use type assertion to tell TypeScript that toolName is a valid key
            const handler = trelloToolHandlers[toolName as keyof typeof trelloToolHandlers];
    
            if (!handler) {
                throw new McpError(
                    ErrorCode.MethodNotFound,
                    `Unknown tool: ${toolName}`
                );
            }
    
            // Execute the tool handler with the provided arguments
            const result = await handler(request.params.arguments);
    
            // Return the result
            return {
                content: [
                    {
                        type: "text",
                        text: JSON.stringify(result, null, 2)
                    }
                ]
            };
        } catch (error) {
            console.error("Error handling tool call:", error);
    
            // If it's already an MCP error, rethrow it
            if (error instanceof McpError) {
                throw error;
            }
    
            // Otherwise, wrap it in an MCP error
            return {
                content: [
                    {
                        type: "text",
                        text: `Error: ${error instanceof Error ? error.message : String(error)}`
                    }
                ],
                isError: true
            };
        }
    });
  • Supporting service method that implements the card move by updating the idList via Trello API.
    async moveCardToList(cardId: string, listId: string): Promise<TrelloCard> {
        return this.updateCard(cardId, { idList: listId });
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/v4lheru/trello-mcp-server'

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