Skip to main content
Glama

get-list-board

Retrieve the Trello board associated with a specific list using its ID to manage project organization and access board-level information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesID of the list to get board for
fieldsNoComma-separated list of board fields to include

Implementation Reference

  • Handler function that checks for credentials, constructs the Trello API URL for retrieving the board associated with the given list ID, optionally includes fields, fetches the data, stringifies it as text content, or returns an error response.
    async ({ listId, fields }) => {
    	try {
    		if (!credentials.apiKey || !credentials.apiToken) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: 'Trello API credentials are not configured',
    					},
    				],
    				isError: true,
    			};
    		}
    
    		const url = new URL(`https://api.trello.com/1/lists/${listId}/board`);
    		url.searchParams.append('key', credentials.apiKey);
    		url.searchParams.append('token', credentials.apiToken);
    		if (fields) url.searchParams.append('fields', fields);
    
    		const response = await fetch(url.toString());
    		const data = await response.json();
    		return {
    			content: [
    				{
    					type: 'text',
    					text: JSON.stringify(data),
    				},
    			],
    		};
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: 'text',
    					text: `Error getting list board: ${error}`,
    				},
    			],
    			isError: true,
    		};
    	}
    }
  • Input schema using Zod validation: requires listId (string), optional fields (string).
    {
    	listId: z.string().describe('ID of the list to get board for'),
    	fields: z.string().optional().describe('Comma-separated list of board fields to include'),
    },
  • Local registration of the 'get-list-board' tool within registerListsTools function, specifying name, input schema, and inline handler.
    // GET /lists/{id}/board - Get the board of a list
    server.tool(
    	'get-list-board',
    	{
    		listId: z.string().describe('ID of the list to get board for'),
    		fields: z.string().optional().describe('Comma-separated list of board fields to include'),
    	},
    	async ({ listId, fields }) => {
    		try {
    			if (!credentials.apiKey || !credentials.apiToken) {
    				return {
    					content: [
    						{
    							type: 'text',
    							text: 'Trello API credentials are not configured',
    						},
    					],
    					isError: true,
    				};
    			}
    
    			const url = new URL(`https://api.trello.com/1/lists/${listId}/board`);
    			url.searchParams.append('key', credentials.apiKey);
    			url.searchParams.append('token', credentials.apiToken);
    			if (fields) url.searchParams.append('fields', fields);
    
    			const response = await fetch(url.toString());
    			const data = await response.json();
    			return {
    				content: [
    					{
    						type: 'text',
    						text: JSON.stringify(data),
    					},
    				],
    			};
    		} catch (error) {
    			return {
    				content: [
    					{
    						type: 'text',
    						text: `Error getting list board: ${error}`,
    					},
    				],
    				isError: true,
    			};
    		}
    	}
    );
  • src/index.ts:89-89 (registration)
    Top-level call to registerListsTools which registers the 'get-list-board' tool (among other lists tools) to the MCP server.
    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