Skip to main content
Glama

archive-cards

Archive Trello cards by specifying their IDs to remove them from active boards while preserving data for future reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardIdsYesIDs of the cards to archive

Implementation Reference

  • src/index.ts:760-816 (registration)
    Registration and inline implementation of the 'archive-cards' MCP tool. The handler archives multiple Trello cards by issuing PUT requests to set 'closed: true' for each card ID provided.
    server.tool(
    	'archive-cards',
    	{
    		cardIds: z.array(z.string()).describe('IDs of the cards to archive'),
    	},
    	async ({ cardIds }) => {
    		try {
    			if (!trelloApiKey || !trelloApiToken) {
    				return {
    					content: [
    						{
    							type: 'text',
    							text: 'Trello API credentials are not configured',
    						},
    					],
    					isError: true,
    				};
    			}
    
    			const results = await Promise.all(
    				cardIds.map(async (cardId) => {
    					const response = await fetch(
    						`https://api.trello.com/1/cards/${cardId}?key=${trelloApiKey}&token=${trelloApiToken}`,
    						{
    							method: 'PUT',
    							headers: {
    								'Content-Type': 'application/json',
    							},
    							body: JSON.stringify({
    								closed: true,
    							}),
    						}
    					);
    					return await response.json();
    				})
    			);
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(results),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error archiving cards: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
  • The handler function for 'archive-cards' tool. It performs batch archiving of Trello cards by mapping over cardIds, sending PUT /cards/{id} with closed: true, and returning JSON results.
    	async ({ cardIds }) => {
    		try {
    			if (!trelloApiKey || !trelloApiToken) {
    				return {
    					content: [
    						{
    							type: 'text',
    							text: 'Trello API credentials are not configured',
    						},
    					],
    					isError: true,
    				};
    			}
    
    			const results = await Promise.all(
    				cardIds.map(async (cardId) => {
    					const response = await fetch(
    						`https://api.trello.com/1/cards/${cardId}?key=${trelloApiKey}&token=${trelloApiToken}`,
    						{
    							method: 'PUT',
    							headers: {
    								'Content-Type': 'application/json',
    							},
    							body: JSON.stringify({
    								closed: true,
    							}),
    						}
    					);
    					return await response.json();
    				})
    			);
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(results),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error archiving cards: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
  • Input schema for the 'archive-cards' tool: an array of card ID strings.
    {
    	cardIds: z.array(z.string()).describe('IDs of the cards to archive'),
    },
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