Skip to main content
Glama
diegofornalha

MCP Server Trello

add_list_to_board

Create a new list on a Trello board by specifying the list name. This tool integrates with MCP Server Trello for managing board activities efficiently.

Instructions

Add a new list to the board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the new list

Implementation Reference

  • src/index.ts:178-191 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, and input schema definition.
    {
      name: 'add_list_to_board',
      description: 'Add a new list to the board',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the new list',
          },
        },
        required: ['name'],
      },
    },
  • MCP tool handler case that validates input and delegates to TrelloClient.addList method.
    case 'add_list_to_board': {
      const validArgs = validateAddListRequest(args);
      const list = await this.trelloClient.addList(validArgs.name);
      return {
        content: [{ type: 'text', text: JSON.stringify(list, null, 2) }],
      };
    }
  • Input validation function ensuring 'name' parameter is a non-empty string.
    export function validateAddListRequest(args: Record<string, unknown>): { name: string } {
      if (!args.name) {
        throw new McpError(ErrorCode.InvalidParams, 'name is required');
      }
      return {
        name: validateString(args.name, 'name'),
      };
    }
  • Core implementation that makes the Trello API POST request to create a new list on the board.
    async addList(name: string): Promise<TrelloList> {
      return this.handleRequest(async () => {
        const response = await this.axiosInstance.post('/lists', {
          name,
          idBoard: this.config.boardId,
        });
        return response.data;
      });
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't cover permissions needed, whether the list is editable after creation, error conditions, or what happens if a duplicate name is used, 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, efficient sentence with zero waste, front-loading the core action. It's appropriately sized for a simple tool, earning full marks for conciseness.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral context, error handling, or return values, making it inadequate for safe and effective use by an AI agent.

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%, so the schema already documents the 'name' parameter fully. The description adds no additional meaning beyond implying a list is created, aligning with the baseline score when schema does the heavy lifting.

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 verb ('add') and resource ('new list to the board'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'add_card_to_list' or 'archive_list', which also modify board components, so it misses full sibling distinction.

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. It doesn't mention prerequisites (e.g., needing an existing board), exclusions, or comparisons to siblings like 'get_lists' for listing or 'archive_list' for removal.

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