Skip to main content
Glama

get_cards

Retrieve cards from a Trello board or specific list to view tasks and manage project workflows.

Instructions

Get cards from a board or specific list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Implementation Reference

  • Handler for the 'get_cards' tool. Extracts board_id and optional list_id from arguments, calls TrelloClient.getCards, and returns JSON stringified cards.
    case 'get_cards': {
      const { board_id, list_id } = (request.params.arguments as { request: GetCardsRequest }).request;
      const cards = await this.trelloClient.getCards(board_id, list_id);
      return {
        content: [{ type: 'text', text: JSON.stringify(cards, null, 2) }],
      };
    }
  • src/index.ts:86-110 (registration)
    Registration of the 'get_cards' tool in the ListToolsRequestHandler, including name, description, and inputSchema.
    {
      name: 'get_cards',
      description: 'Get cards from a board or specific list',
      inputSchema: {
        type: 'object',
        properties: {
          request: {
            type: 'object',
            properties: {
              board_id: {
                type: 'string',
                description: 'ID of the board',
              },
              list_id: {
                type: 'string',
                description: 'Optional ID of a specific list',
              },
            },
            required: ['board_id'],
          },
        },
        required: ['request'],
        title: 'get_cardsArguments',
      },
    },
  • TypeScript interface definition for GetCardsRequest, used for type-checking the tool arguments in the handler.
    export interface GetCardsRequest {
      board_id: string;
      list_id?: string;
    }
  • Core implementation of fetching cards from Trello API, either from a specific list or all board cards, called by the tool handler.
    async getCards(boardId: string, listId?: string): Promise<Card[]> {
      const endpoint = listId
        ? `${this.baseUrl}/lists/${listId}/cards`
        : `${this.baseUrl}/boards/${boardId}/cards`;
      const response = await axios.get(`${endpoint}?${this.getAuthParams()}`);
      return response.data;
    }
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action 'Get cards' without any details on permissions, rate limits, pagination, or response format. This is inadequate for a tool with potential complexity, as it fails to describe how the tool behaves beyond the basic operation.

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: 'Get cards from a board or specific list'. It is front-loaded with the core action and resource, with no unnecessary words. This makes it highly concise and well-structured for quick understanding.

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 low schema coverage, the description is incomplete. It does not address behavioral aspects like safety, response handling, or error conditions, and it lacks differentiation from sibling tools. For a tool that likely returns multiple items, more context on output and usage is needed.

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 input schema has 1 parameter (a nested object with 'board_id' and optional 'list_id'), but schema description coverage is 0%, meaning parameters are undocumented in the schema. The description mentions 'board or specific list', which hints at the parameters but does not explain their semantics, formats, or constraints. This adds minimal value beyond the schema's structure.

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

Purpose3/5

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

The description states the tool's purpose as 'Get cards from a board or specific list', which is clear but vague. It specifies the verb 'Get' and resources 'cards', but lacks specificity about scope (e.g., all cards, filtered cards) and does not distinguish from siblings like 'get_card_details' or 'get_lists'. This makes it minimally adequate but with gaps in differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention when to prefer 'get_cards' over 'get_card_details' for detailed card info or 'get_lists' for list-level operations, nor does it specify prerequisites or exclusions. This leaves the agent without clear usage context.

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