Skip to main content
Glama

get_lists

Retrieve all lists from a Trello board using the board ID to organize and manage tasks, cards, and workflows.

Instructions

Get all lists in a board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Implementation Reference

  • The handler function for the 'get_lists' tool in the CallToolRequestSchema handler. It parses the arguments, calls trelloClient.getLists(board_id), and returns the JSON stringified lists.
    case 'get_lists': {
      const { board_id } = (request.params.arguments as { request: GetListsRequest }).request;
      const lists = await this.trelloClient.getLists(board_id);
      return {
        content: [{ type: 'text', text: JSON.stringify(lists, null, 2) }],
      };
    }
  • src/index.ts:65-84 (registration)
    Registration of the 'get_lists' tool in the ListToolsRequestSchema handler, including name, description, and inputSchema.
    {
      name: 'get_lists',
      description: 'Get all lists in a board',
      inputSchema: {
        type: 'object',
        properties: {
          request: {
            type: 'object',
            properties: {
              board_id: {
                type: 'string',
                description: 'ID of the board',
              },
            },
            required: ['board_id'],
          },
        },
        required: ['request'],
        title: 'get_listsArguments',
      },
  • TypeScript interface defining the input parameters for get_lists request.
    export interface GetListsRequest {
      board_id: string;
    }
  • The TrelloClient method that fetches lists for a board via Trello API, called by the tool handler.
    async getLists(boardId: string): Promise<List[]> {
      const response = await axios.get(
        `${this.baseUrl}/boards/${boardId}/lists?${this.getAuthParams()}`
      );
      return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets' lists, implying a read operation, but doesn't mention any constraints like permissions needed, rate limits, pagination behavior, or what happens if the board_id is invalid. This leaves significant gaps for a tool with no annotation coverage.

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 that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the tool has no annotations, no output schema, and low schema description coverage, the description is incomplete. It doesn't provide enough context about behavior, parameters, or output to adequately guide an AI agent, especially for a tool that interacts with a board system where details like permissions or data format matter.

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

Parameters2/5

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

The schema description coverage is 0%, with only one parameter 'board_id' documented in the schema without any description. The tool description doesn't add any parameter details beyond what's implied by 'in a board', failing to compensate for the low coverage. It doesn't explain what format board_id should be in or where to find it.

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 'Get' and resource 'all lists in a board', making the purpose immediately understandable. It doesn't distinguish from siblings like 'get_boards' or 'get_cards', but it's specific enough to understand what resource is being retrieved.

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 'get_boards' or 'get_cards'. The description only states what it does without context about when it's appropriate or what prerequisites might be needed.

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/andypost/mcp-server-ts-trello'

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