Skip to main content
Glama
diegofornalha

MCP Server Trello

archive_list

Archive a Trello list by providing its ID; simplifies board management and keeps workspaces organized while integrating with MCP Server Trello.

Instructions

Send a list to the archive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesID of the list to archive

Implementation Reference

  • The core handler function that archives a Trello list by sending a PUT request to set the list's closed status to true.
    async archiveList(listId: string): Promise<TrelloList> {
      return this.handleRequest(async () => {
        const response = await this.axiosInstance.put(`/lists/${listId}/closed`, {
          value: true,
        });
        return response.data;
      });
    }
  • src/index.ts:192-205 (registration)
    Tool registration in the ListTools response, defining name, description, and input schema.
    {
      name: 'archive_list',
      description: 'Send a list to the archive',
      inputSchema: {
        type: 'object',
        properties: {
          listId: {
            type: 'string',
            description: 'ID of the list to archive',
          },
        },
        required: ['listId'],
      },
    },
  • src/index.ts:282-288 (registration)
    Dispatch handler in CallToolRequest that validates args and calls the trelloClient.archiveList method.
    case 'archive_list': {
      const validArgs = validateArchiveListRequest(args);
      const list = await this.trelloClient.archiveList(validArgs.listId);
      return {
        content: [{ type: 'text', text: JSON.stringify(list, null, 2) }],
      };
    }
  • Input validation function ensuring listId is provided and is a string.
    export function validateArchiveListRequest(args: Record<string, unknown>): { listId: string } {
      if (!args.listId) {
        throw new McpError(ErrorCode.InvalidParams, 'listId is required');
      }
      return {
        listId: validateString(args.listId, 'listId'),
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose whether archiving is reversible, requires specific permissions, affects related data, or has side effects, leaving significant gaps for a mutation tool.

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

Conciseness5/5

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

The description is a single, direct sentence with zero wasted words, efficiently conveying the core action. It is appropriately sized for a simple tool and front-loaded with essential information.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavior, outcomes, error conditions, or integration with sibling tools, failing to compensate for the missing structured data.

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

Parameters3/5

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

Schema description coverage is 100%, with the single parameter 'listId' clearly documented in the schema. The description adds no additional parameter context beyond implying 'listId' is needed, meeting the baseline for high schema coverage without extra value.

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

Purpose4/5

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

The description clearly states the action ('Send') and target resource ('a list to the archive'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'archive_card' or specify what 'archive' means in this context, preventing a perfect score.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'archive_card' or other list-related operations. The description lacks context about prerequisites, consequences, or typical use cases, offering minimal practical direction.

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

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

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