Skip to main content
Glama

archive-all-cards-in-list

Archive all cards in a specified Trello list to clean up completed tasks or remove outdated items. Provide the list ID to execute this bulk archiving action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesID of the list to archive all cards in

Implementation Reference

  • The handler function that implements the core logic of the tool by sending a POST request to the Trello API to archive all cards in the given list ID. Includes credential validation, API call, response handling, and error management.
    async ({ listId }) => {
    	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}/archiveAllCards?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    			{
    				method: 'POST',
    				headers: {
    					'Content-Type': 'application/json',
    				},
    			}
    		);
    		const data = await response.json();
    		return {
    			content: [
    				{
    					type: 'text',
    					text: JSON.stringify(data),
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text',
    					text: `Error archiving all cards in list: ${error}`,
    				},
    			],
    			isError: true,
    		};
    	}
    }
  • Zod input schema defining the required 'listId' parameter as a string with description.
    {
    	listId: z.string().describe('ID of the list to archive all cards in'),
    },
  • Registration of the 'archive-all-cards-in-list' tool on the MCP server using server.tool(), including schema and handler.
    server.tool(
    	'archive-all-cards-in-list',
    	{
    		listId: z.string().describe('ID of the list to archive all cards in'),
    	},
    	async ({ listId }) => {
    		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}/archiveAllCards?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    				{
    					method: 'POST',
    					headers: {
    						'Content-Type': 'application/json',
    					},
    				}
    			);
    			const data = await response.json();
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(data),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error archiving all cards in list: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
  • src/index.ts:89-89 (registration)
    Invocation of registerListsTools which includes the registration of the archive-all-cards-in-list tool among other list tools.
    registerListsTools(server, credentials);
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