Skip to main content
Glama

create-list

Add a new list to a Trello board by specifying the board ID, list name, and optional position to organize project tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board to create the list in
nameYesName of the list
positionNoPosition of the list (e.g. "top", "bottom", or a number)

Implementation Reference

  • Handler function that creates a new Trello list using POST /lists endpoint with provided boardId, name, and optional position.
    	async ({ boardId, name, position = 'bottom' }) => {
    		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?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    				{
    					method: 'POST',
    					headers: {
    						'Content-Type': 'application/json',
    					},
    					body: JSON.stringify({
    						name,
    						idBoard: boardId,
    						pos: position,
    					}),
    				}
    			);
    			const data = await response.json();
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(data),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error creating list: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
  • Input schema using Zod for validating parameters: boardId, name, and optional position.
    {
    	boardId: z.string().describe('ID of the board to create the list in'),
    	name: z.string().describe('Name of the list'),
    	position: z.string().optional().describe('Position of the list (e.g. "top", "bottom", or a number)'),
    },
  • The server.tool() call within registerListsTools that registers the 'create-list' tool, including schema and handler.
    	'create-list',
    	{
    		boardId: z.string().describe('ID of the board to create the list in'),
    		name: z.string().describe('Name of the list'),
    		position: z.string().optional().describe('Position of the list (e.g. "top", "bottom", or a number)'),
    	},
    	async ({ boardId, name, position = 'bottom' }) => {
    		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?key=${credentials.apiKey}&token=${credentials.apiToken}`,
    				{
    					method: 'POST',
    					headers: {
    						'Content-Type': 'application/json',
    					},
    					body: JSON.stringify({
    						name,
    						idBoard: boardId,
    						pos: position,
    					}),
    				}
    			);
    			const data = await response.json();
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(data),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error creating list: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
  • src/index.ts:89-89 (registration)
    Invocation of registerListsTools in the main server setup, which registers all list tools including 'create-list'.
    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