Skip to main content
Glama

update_card

Modify existing Trello card details including name, description, due date, status, position, or archive status to keep project tasks current and organized.

Instructions

Update properties of an existing Trello card. Use this to change card details like name, description, due date, or status.

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 update (you can get this from board details or card searches)
nameNoNew name/title for the card
descNoNew description for the card
closedNoSet to true to archive the card, false to unarchive
dueNoSet due date (ISO 8601 format) or null to remove due date
dueCompleteNoMark the due date as complete (true) or incomplete (false)
idListNoMove card to a different list by providing the list ID
posNoChange position in the list: "top", "bottom", or specific number

Implementation Reference

  • The handler function for updating a Trello card, which validates inputs and calls the Trello client.
    export async function handleUpdateCard(args: unknown) {
      try {
        const updateData = validateUpdateCard(args);
        const { apiKey, token, cardId, ...updates } = updateData;
        
        const client = new TrelloClient({ apiKey, token });
        const response = await client.updateCard(cardId, updates);
        const card = response.data;
        
        const result = {
          summary: `Updated 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,
            labels: card.labels?.map(label => ({
              id: label.id,
  • Schema definition for validating the update_card input arguments.
    export const updateCardSchema = z.object({
      apiKey: z.string().min(1, 'API key is required'),
      token: z.string().min(1, 'Token is required'),
      cardId: trelloIdSchema,
      name: z.string().min(1).max(16384).optional(),
      desc: z.string().max(16384).optional(),
      closed: z.boolean().optional(),
      due: z.string().datetime().nullable().optional(),
      dueComplete: z.boolean().optional(),
      idList: trelloIdOptionalSchema,
      pos: z.union([z.number().min(0), z.enum(['top', 'bottom'])]).optional(),
      idMembers: z.array(trelloIdSchema).optional(),
      idLabels: z.array(trelloIdSchema).optional()
    });
  • Definition and registration of the update_card tool.
    export const updateCardTool: Tool = {
      name: 'update_card',
      description: 'Update properties of an existing Trello card. Use this to change card details like name, description, due date, or status.',
      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 update (you can get this from board details or card searches)',
            pattern: '^[a-f0-9]{24}$'
          },
          name: {
            type: 'string',
            description: 'New name/title for the card'
          },
          desc: {
            type: 'string',
            description: 'New description for the card'
          },
          closed: {
            type: 'boolean',
            description: 'Set to true to archive the card, false to unarchive'
          },
          due: {
            type: ['string', 'null'],
            format: 'date-time',
            description: 'Set due date (ISO 8601 format) or null to remove due date'
          },
          dueComplete: {
            type: 'boolean',
            description: 'Mark the due date as complete (true) or incomplete (false)'
          },
          idList: {
            type: 'string',
            description: 'Move card to a different list by providing the list ID',
            pattern: '^[a-f0-9]{24}$'
          },
          pos: {
            oneOf: [
              { type: 'number', minimum: 0 },
              { type: 'string', enum: ['top', 'bottom'] }
            ],
            description: 'Change position in the list: "top", "bottom", or specific number'
          }
        },
        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 mutation operation ('Update properties'), it doesn't address important behavioral aspects like required permissions, whether changes are reversible, rate limits, error conditions, or what happens when only some parameters are provided. The description mentions changing 'status' (implied via closed/dueComplete parameters) but doesn't clarify behavioral implications.

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 efficiently structured in two sentences: the first states the core purpose, the second provides usage guidance with specific examples. Every word serves a purpose with zero wasted text, and the most important information ('Update properties of an existing Trello card') is front-loaded.

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 mutation tool with 10 parameters, no annotations, and no output schema, the description is minimally adequate. It identifies the tool's purpose and provides some usage examples, but doesn't address behavioral aspects, error handling, or response format. The high schema coverage helps, but more behavioral context would be beneficial given this is a write operation.

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 10 parameters thoroughly. The description adds marginal value by listing examples of updatable properties ('name, description, due date, or status'), but doesn't provide additional semantic context beyond what's in the parameter descriptions. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 ('Update') and resource ('existing Trello card'), and provides specific examples of what can be changed ('name, description, due date, or status'). It distinguishes this from create_card by specifying 'existing' card, but doesn't explicitly differentiate from move_card which also updates card properties.

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 by stating 'Use this to change card details' and listing specific properties, but doesn't provide explicit guidance on when to choose this tool versus alternatives like move_card (which appears to specialize in card movement) or when not to use it. No prerequisites or exclusions are mentioned.

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