Skip to main content
Glama

get_boards

Retrieve all Trello boards for the authenticated user to view and manage workspace organization.

Instructions

Get all boards for the authenticated user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_boards' tool call. It invokes the TrelloClient's getBoards method and returns the result as a JSON-formatted text response.
    case 'get_boards':
      const boards = await this.trelloClient.getBoards();
      return {
        content: [{ type: 'text', text: JSON.stringify(boards, null, 2) }],
      };
  • Input schema definition for the 'get_boards' tool, specifying an empty object (no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
      title: 'get_boardsArguments',
    },
  • src/index.ts:56-64 (registration)
    Tool registration in the ListTools response, defining name, description, and schema for 'get_boards'.
    {
      name: 'get_boards',
      description: 'Get all boards for the authenticated user',
      inputSchema: {
        type: 'object',
        properties: {},
        title: 'get_boardsArguments',
      },
    },
  • The TrelloClient method that implements the core logic for retrieving the authenticated user's boards from the Trello API.
    async getBoards(): Promise<Board[]> {
      const response = await axios.get(
        `${this.baseUrl}/members/me/boards?${this.getAuthParams()}`
      );
      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 it retrieves boards without detailing behavior. It lacks information on rate limits, pagination, error handling, or what 'all boards' entails (e.g., archived ones). This is inadequate for a tool with zero 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 with no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand 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 no annotations, no output schema, and a read operation, the description is incomplete. It doesn't explain return values (e.g., board structure), authentication needs, or potential limitations, leaving gaps for an AI agent to use it effectively.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema coverage, so no parameter documentation is needed. The description doesn't add param details, but since there are none, a baseline of 4 is appropriate as it doesn't miss anything required.

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 action ('Get') and resource ('all boards'), specifying it's for the authenticated user. It distinguishes from siblings like get_card_details and get_cards by focusing on boards rather than cards or lists, though it doesn't explicitly contrast with update_card.

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 (like authentication), compare with get_lists for list retrieval, or specify scenarios where boards vs. cards are needed, leaving usage context unclear.

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