Skip to main content
Glama

trello_get_card_checklists

Retrieve all checklists and their items for a specific Trello card to track tasks and progress.

Instructions

Get all checklists and their items for a specific Trello card.

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)
cardIdYesID of the card to get checklists for
checkItemsNoInclude checklist items in responseall
fieldsNoOptional: specific fields to include (e.g., ["name", "pos"])

Implementation Reference

  • The handler function that executes the Trello get checklists logic.
    export async function handleTrelloGetCardChecklists(args: unknown) {
      try {
        const { apiKey, token, cardId, checkItems, fields } = validateGetCardChecklists(args);
        const client = new TrelloClient({ apiKey, token });
        
        const response = await client.getCardChecklists(cardId, {
          ...(checkItems && { checkItems }),
          ...(fields && { fields })
        });
        const checklists = response.data;
        
        const result = {
          summary: `Found ${checklists.length} checklist(s) for card`,
          cardId,
          checklists: checklists.map(checklist => ({
            id: checklist.id,
            name: checklist.name,
            position: checklist.pos,
            checkItems: checklist.checkItems?.map((item: any) => ({
              id: item.id,
              name: item.name,
              state: item.state,
              position: item.pos,
              due: item.due,
              nameData: item.nameData
            })) || []
          })),
          rateLimit: response.rateLimit
        };
        
        return {
          content: [
            {
              type: 'text' as const,
              text: JSON.stringify(result, null, 2)
            }
          ]
        };
      } catch (error) {
        const errorMessage = error instanceof z.ZodError 
          ? formatValidationError(error)
          : error instanceof Error 
            ? error.message 
  • Tool definition including input schema for 'trello_get_card_checklists'.
    export const trelloGetCardChecklistsTool: Tool = {
      name: 'trello_get_card_checklists',
      description: 'Get all checklists and their items for a specific Trello card.',
      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)'
          },
          cardId: {
            type: 'string',
            description: 'ID of the card to get checklists for',
            pattern: '^[a-f0-9]{24}$'
          },
          checkItems: {
            type: 'string',
            enum: ['all', 'none'],
            description: 'Include checklist items in response',
            default: 'all'
          },
          fields: {
            type: 'array',
            items: { type: 'string' },
            description: 'Optional: specific fields to include (e.g., ["name", "pos"])'
          }
        },
        required: ['apiKey', 'token', 'cardId']
      }
    };
Behavior2/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 states it 'Get all checklists and their items,' implying a read-only operation, but does not cover aspects like authentication needs (though hinted in schema), rate limits, error handling, or response format. 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 unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured.

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 and no output schema, the description is incomplete. It lacks details on behavioral traits, response format, error cases, or usage context. For a tool with 5 parameters and complex operations like API calls, this minimal description does not provide enough context for effective use.

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 does not add any meaning beyond the schema, such as explaining parameter interactions or usage examples. Baseline 3 is appropriate when the schema handles parameter documentation effectively.

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 the resource 'all checklists and their items for a specific Trello card,' making the purpose evident. However, it does not explicitly differentiate from siblings like 'get_card' or 'trello_get_card_attachments,' which might also retrieve card-related data, so it lacks sibling 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, such as 'get_card' for general card info or other sibling tools. It implies usage by specifying 'for a specific Trello card' but offers no explicit context, exclusions, or alternatives.

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