Skip to main content
Glama

trello_create_list

Create a new list in a Trello board to organize workflow columns like "To Do", "In Progress", or "Done" for project management.

Instructions

Create a new list in a Trello board. Use this to add workflow columns like "To Do", "In Progress", or "Done".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesTrello API key (automatically provided by Claude.app from your stored credentials)
tokenYesTrello API token (automatically provided by Claude.app from your stored credentials)
nameYesName of the new list (e.g., "To Do", "In Progress", "Done")
idBoardYesID of the board where the list will be created (you can get this from list_boards)
posNoPosition of the list in the board: "top", "bottom", or specific numberbottom

Implementation Reference

  • The handler function that performs the API call to create a Trello list.
    export async function handleTrelloCreateList(args: unknown) {
      try {
        const listData = validateCreateList(args);
        const { apiKey, token, ...createData } = listData;
        
        const client = new TrelloClient({ apiKey, token });
        const response = await client.createList({
          name: createData.name,
          idBoard: createData.idBoard,
          ...(createData.pos !== undefined && { pos: createData.pos })
        });
        const list = response.data;
        
        const result = {
          summary: `Created list: ${list.name}`,
          list: {
            id: list.id,
            name: list.name,
            boardId: list.idBoard,
            position: list.pos,
            closed: list.closed,
            subscribed: list.subscribed
          },
          rateLimit: response.rateLimit
        };
        
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof z.ZodError 
          ? formatValidationError(error)
          : error instanceof Error 
            ? error.message 
            : 'Unknown error occurred';
            
        return {
          content: [
            {
              type: 'text' as const,
              text: `Error creating list: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
    }
  • Input validation schema for creating a Trello list.
    const validateCreateList = (args: unknown) => {
      const schema = z.object({
        apiKey: z.string().min(1, 'API key is required'),
        token: z.string().min(1, 'Token is required'),
        name: z.string().min(1, 'List name is required'),
        idBoard: z.string().regex(/^[a-f0-9]{24}$/, 'Invalid board ID format'),
        pos: z.union([z.number().min(0), z.enum(['top', 'bottom'])]).optional()
      });
      
      return schema.parse(args);
    };
  • Tool definition for 'trello_create_list'.
    export const trelloCreateListTool: Tool = {
      name: 'trello_create_list',
      description: 'Create a new list in a Trello board. Use this to add workflow columns like "To Do", "In Progress", or "Done".',
      inputSchema: {
        type: 'object',
        properties: {
          apiKey: {
            type: 'string',
            description: 'Trello API key (automatically provided by Claude.app from your stored credentials)'
          },
          token: {
            type: 'string',
            description: 'Trello API token (automatically provided by Claude.app from your stored credentials)'
          },
          name: {
            type: 'string',
            description: 'Name of the new list (e.g., "To Do", "In Progress", "Done")',
            minLength: 1
          },
          idBoard: {
            type: 'string',
            description: 'ID of the board where the list will be created (you can get this from list_boards)',
            pattern: '^[a-f0-9]{24}$'
          },
          pos: {
            oneOf: [
              { type: 'number', minimum: 0 },
              { type: 'string', enum: ['top', 'bottom'] }
            ],
            description: 'Position of the list in the board: "top", "bottom", or specific number',
            default: 'bottom'
          }
        },
        required: ['apiKey', 'token', 'name', 'idBoard']
      }
    };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it states this is a creation operation, it doesn't disclose important behavioral traits like authentication requirements (though parameters suggest them), permission needs, whether creation is idempotent, error conditions, or what happens on success. The description provides minimal behavioral context beyond the basic action.

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 perfectly concise with two sentences that each earn their place. The first states the core purpose, the second provides usage context with concrete examples. No wasted words, well-structured, and front-loaded with the essential information.

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

Completeness3/5

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

For a creation tool with no annotations and no output schema, the description is adequate but has clear gaps. It explains what the tool does and provides usage examples, but doesn't address behavioral aspects like authentication, permissions, error handling, or what the tool returns. The 100% schema coverage helps, but for a mutation tool, more behavioral context would be beneficial.

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 all parameters thoroughly. The description adds minimal parameter semantics - it only mentions the 'name' parameter through examples ('"To Do", "In Progress", or "Done"'), but doesn't provide additional context beyond what's in the schema descriptions. This meets the baseline for high schema coverage.

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

Purpose5/5

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

The description clearly states the specific action ('Create a new list'), resource ('in a Trello board'), and provides concrete examples of typical use cases ('workflow columns like "To Do", "In Progress", or "Done"'). It distinguishes this tool from sibling tools that create cards, get board details, or perform other Trello operations.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool ('to add workflow columns'), which implicitly distinguishes it from tools like create_card (for creating cards within lists) or get_lists (for reading lists). However, it doesn't explicitly state when NOT to use it or mention specific alternatives by name.

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/kocakli/Trello-Desktop-MCP'

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