Skip to main content
Glama

trello_get_list_cards

Retrieve all cards from a specific Trello list to view tasks and items in a workflow column. Filter by open, closed, or all cards and select specific fields to display.

Instructions

Get all cards in a specific Trello list. Use this to see all tasks/items in a workflow column.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesTrello API key (automatically provided by Claude.app from your stored credentials)
tokenYesTrello API token (automatically provided by Claude.app from your stored credentials)
listIdYesID of the list to get cards from (you can get this from get_lists)
filterNoFilter cards by status: "open" for active cards, "closed" for archived cards, "all" for bothopen
fieldsNoOptional: specific fields to include (e.g., ["name", "desc", "due", "labels", "members"])

Implementation Reference

  • The handler function that fetches cards from a specific Trello list using the Trello client.
    export async function handleTrelloGetListCards(args: unknown) {
      try {
        const { apiKey, token, listId, filter, fields } = validateGetListCards(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getListCards(listId, { 
          ...(filter && { filter }),
          ...(fields && { fields })
        });
        const cards = response.data;
        
        const result = {
          summary: `Found ${cards.length} ${filter || 'open'} card(s) in list`,
          listId,
          cards: cards.map(card => ({
            id: card.id,
            name: card.name,
            description: card.desc || 'No description',
            url: card.shortUrl,
            listId: card.idList,
            boardId: card.idBoard,
            position: card.pos,
            due: card.due,
            dueComplete: card.dueComplete,
            closed: card.closed,
            lastActivity: card.dateLastActivity,
            labels: card.labels?.map(label => ({
              id: label.id,
              name: label.name,
              color: label.color
            })) || [],
            members: card.members?.map(member => ({
              id: member.id,
              fullName: member.fullName,
              username: member.username
            })) || []
  • The tool definition including the schema for inputs and the tool name.
    export const trelloGetListCardsTool: Tool = {
      name: 'trello_get_list_cards',
      description: 'Get all cards in a specific Trello list. Use this to see all tasks/items in a workflow column.',
      inputSchema: {
        type: 'object',
        properties: {
          apiKey: {
            type: 'string',
            description: 'Trello API key (automatically provided by Claude.app from your stored credentials)'
          },
          token: {
            type: 'string',
            description: 'Trello API token (automatically provided by Claude.app from your stored credentials)'
          },
          listId: {
            type: 'string',
            description: 'ID of the list to get cards from (you can get this from get_lists)',
            pattern: '^[a-f0-9]{24}$'
          },
          filter: {
            type: 'string',
            enum: ['all', 'open', 'closed'],
            description: 'Filter cards by status: "open" for active cards, "closed" for archived cards, "all" for both',
            default: 'open'
          },
          fields: {
            type: 'array',
            items: { type: 'string' },
            description: 'Optional: specific fields to include (e.g., ["name", "desc", "due", "labels", "members"])'
          }
        },
        required: ['apiKey', 'token', 'listId']
      }
    };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't mention authentication requirements (though parameters suggest it), rate limits, pagination behavior, error conditions, or what the response looks like. For a read operation with 5 parameters and no annotations, this leaves significant gaps in understanding how the tool behaves.

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 perfectly concise - two sentences that directly state the tool's purpose and provide a helpful analogy. Every word earns its place, and the information is front-loaded with no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read operation with 5 parameters, 100% schema coverage, but no annotations and no output schema, the description is minimally adequate. It states the purpose clearly but doesn't provide enough behavioral context about what to expect from the response, error handling, or operational constraints that would be needed for robust agent usage.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline of 3 is appropriate when the schema does all the heavy lifting for parameter documentation.

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 cards in a specific Trello list'), and provides a helpful analogy ('tasks/items in a workflow column'). However, it doesn't explicitly differentiate from sibling tools like 'trello_get_board_cards' or 'get_card', which also retrieve cards but with different scopes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context ('to see all tasks/items in a workflow column') but doesn't explicitly state when to use this tool versus alternatives like 'trello_get_board_cards' (for all cards on a board) or 'get_card' (for a single card). It mentions getting listId from 'get_lists', which is helpful but not comprehensive guidance on tool selection.

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/kocakli/Trello-Desktop-MCP'

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