Skip to main content
Glama

get_card

Retrieve detailed information about a specific Trello card including content, status, members, and attachments to track project progress and team collaboration.

Instructions

Get detailed information about a specific Trello card, including its content, status, members, and attachments.

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 retrieve (you can get this from board details or searches)
includeDetailsNoInclude additional details like members, labels, checklists, and activity badges

Implementation Reference

  • The `handleGetCard` function handles the logic for executing the `get_card` tool by calling the TrelloClient and returning the card data.
    export async function handleGetCard(args: unknown) {
      try {
        const { apiKey, token, cardId, includeDetails } = validateGetCard(args);
        
        const client = new TrelloClient({ apiKey, token });
        const response = await client.getCard(cardId, includeDetails);
        const card = response.data;
        
        const result = {
          summary: `Card: ${card.name}`,
          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,
            ...(includeDetails && {
              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,
                initials: member.initials
              })) || [],
              checklists: card.checklists?.map(checklist => ({
                id: checklist.id,
                name: checklist.name,
                checkItems: checklist.checkItems?.map(item => ({
                  id: item.id,
                  name: item.name,
                  state: item.state,
                  due: item.due
                })) || []
              })) || [],
              badges: card.badges ? {
                votes: card.badges.votes,
                comments: card.badges.comments,
                attachments: card.badges.attachments,
                checkItems: card.badges.checkItems,
                checkItemsChecked: card.badges.checkItemsChecked,
                description: card.badges.description
              } : undefined
            })
          },
          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 
            : 'Unknown error occurred';
            
        return {
          content: [
            {
              type: 'text' as const,
              text: `Error getting card: ${errorMessage}`
            }
          ],
          isError: true
        };
      }
  • The `getCardTool` constant defines the name, description, and input schema for the `get_card` tool.
    export const getCardTool: Tool = {
      name: 'get_card',
      description: 'Get detailed information about a specific Trello card, including its content, status, members, and attachments.',
      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 retrieve (you can get this from board details or searches)',
            pattern: '^[a-f0-9]{24}$'
          },
          includeDetails: {
            type: 'boolean',
            description: 'Include additional details like members, labels, checklists, and activity badges',
            default: false
          }
        },
        required: ['apiKey', 'token', 'cardId']
      }
    };
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. While it indicates this is a read operation ('Get'), it doesn't address important behavioral aspects: authentication requirements (though schema covers apiKey/token), rate limits, error conditions, what happens when includeDetails is false vs true, or the format/structure of returned information. The description is too minimal 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 front-loads the core purpose. Every word earns its place - 'detailed information' sets expectations, and the list of included data types ('content, status, members, and attachments') provides useful scope without verbosity. No wasted words or redundant information.

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?

For a tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'detailed information' actually includes beyond the listed examples, doesn't describe the response format, and provides no behavioral context about authentication, errors, or limitations. Given the complexity of retrieving card data with optional details, more comprehensive guidance is needed.

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 fully documents all 4 parameters. The description mentions 'including its content, status, members, and attachments' which loosely relates to the includeDetails parameter, but doesn't add meaningful semantic context beyond what the schema provides. This meets the baseline for high schema coverage.

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 tool's purpose: 'Get detailed information about a specific Trello card, including its content, status, members, and attachments.' It specifies the verb ('Get'), resource ('Trello card'), and scope of information returned. However, it doesn't explicitly differentiate from sibling tools like 'trello_get_card_actions' or 'trello_get_card_attachments' that retrieve more specific subsets of card data.

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 doesn't mention when this comprehensive card retrieval is preferable over more specific sibling tools like 'trello_get_card_actions' (for activity history) or 'trello_get_card_attachments' (just for files). There's also no mention of prerequisites like needing the card ID first.

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