Skip to main content
Glama

move-all-cards-in-list

Transfer all cards from one Trello list to another list, either within the same board or to a different board, using list and board IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesID of the source list
destinationBoardIdYesID of the destination board
destinationListIdYesID of the destination list

Implementation Reference

  • Handler function that executes the tool by making a POST request to Trello's /lists/{listId}/moveAllCards endpoint, supplying the destination board and list IDs in the body. Handles credentials check and errors.
    async ({ listId, destinationBoardId, destinationListId }) => {
    	try {
    		if (!credentials.apiKey || !credentials.apiToken) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: 'Trello API credentials are not configured',
    					},
    				],
    				isError: true,
    			};
    		}
    
    		const response = await fetch(
    			`https://api.trello.com/1/lists/${listId}/moveAllCards?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    			{
    				method: 'POST',
    				headers: {
    					'Content-Type': 'application/json',
    				},
    				body: JSON.stringify({
    					idBoard: destinationBoardId,
    					idList: destinationListId,
    				}),
    			}
    		);
    		const data = await response.json();
    		return {
    			content: [
    				{
    					type: 'text',
    					text: JSON.stringify(data),
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text',
    					text: `Error moving all cards in list: ${error}`,
    				},
    			],
    			isError: true,
    		};
    	}
    }
  • Input schema using Zod validation for the tool parameters: source list ID, destination board ID, and destination list ID.
    {
    	listId: z.string().describe('ID of the source list'),
    	destinationBoardId: z.string().describe('ID of the destination board'),
    	destinationListId: z.string().describe('ID of the destination list'),
    },
  • Registration of the 'move-all-cards-in-list' tool using server.tool(), including inline schema and handler within the registerListsTools function.
    server.tool(
    	'move-all-cards-in-list',
    	{
    		listId: z.string().describe('ID of the source list'),
    		destinationBoardId: z.string().describe('ID of the destination board'),
    		destinationListId: z.string().describe('ID of the destination list'),
    	},
    	async ({ listId, destinationBoardId, destinationListId }) => {
    		try {
    			if (!credentials.apiKey || !credentials.apiToken) {
    				return {
    					content: [
    						{
    							type: 'text',
    							text: 'Trello API credentials are not configured',
    						},
    					],
    					isError: true,
    				};
    			}
    
    			const response = await fetch(
    				`https://api.trello.com/1/lists/${listId}/moveAllCards?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    				{
    					method: 'POST',
    					headers: {
    						'Content-Type': 'application/json',
    					},
    					body: JSON.stringify({
    						idBoard: destinationBoardId,
    						idList: destinationListId,
    					}),
    				}
    			);
    			const data = await response.json();
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(data),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error moving all cards in list: ${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/adriangrahldev/advanced-trello-mcp-server'

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