Skip to main content
Glama

move-cards

Move Trello cards between lists or reorder them within lists to organize project workflows and track task progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardsYes

Implementation Reference

  • Handler function that moves multiple Trello cards to specified lists using parallel API PUT requests.
    async ({ cards }) => {
    	try {
    		const results = await Promise.all(
    			cards.map(async (card) => {
    				const response = await fetch(
    					`https://api.trello.com/1/cards/${card.cardId}?key=${trelloApiKey}&token=${trelloApiToken}`,
    					{
    						method: 'PUT',
    						headers: {
    							'Content-Type': 'application/json',
    						},
    						body: JSON.stringify({
    							idList: card.listId,
    							pos: card.position || 'bottom',
    						}),
    					}
    				);
    				return await response.json();
    			})
    		);
    		return {
    			content: [
    				{
    					type: 'text',
    					text: JSON.stringify(results),
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text',
    					text: `Error moving cards: ${error}`,
    				},
    			],
    			isError: true,
    		};
    	}
    }
  • Zod input schema for the move-cards tool, accepting an array of card objects with cardId, listId, and optional position.
    {
    	cards: z.array(
    		z.object({
    			cardId: z.string().describe('ID of the card to move'),
    			listId: z.string().describe('ID of the destination list'),
    			position: z.string().optional().describe('Position in the list (e.g. "top", "bottom")'),
    		})
    	),
    },
  • src/index.ts:420-471 (registration)
    Registration of the 'move-cards' tool using server.tool, including inline schema and handler.
    server.tool(
    	'move-cards',
    	{
    		cards: z.array(
    			z.object({
    				cardId: z.string().describe('ID of the card to move'),
    				listId: z.string().describe('ID of the destination list'),
    				position: z.string().optional().describe('Position in the list (e.g. "top", "bottom")'),
    			})
    		),
    	},
    	async ({ cards }) => {
    		try {
    			const results = await Promise.all(
    				cards.map(async (card) => {
    					const response = await fetch(
    						`https://api.trello.com/1/cards/${card.cardId}?key=${trelloApiKey}&token=${trelloApiToken}`,
    						{
    							method: 'PUT',
    							headers: {
    								'Content-Type': 'application/json',
    							},
    							body: JSON.stringify({
    								idList: card.listId,
    								pos: card.position || 'bottom',
    							}),
    						}
    					);
    					return await response.json();
    				})
    			);
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(results),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error moving cards: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
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/praveencs87/trello-mcp'

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