Skip to main content
Glama

update_card

Modify card details in Trello by providing the card ID and updated properties to change information on existing cards.

Instructions

Update properties of a specific card

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestYes

Implementation Reference

  • Handler logic for the 'update_card' tool: parses arguments, calls TrelloClient.updateCard, and returns the updated card as JSON.
    case 'update_card': {
      const { card_id, update_data } = (request.params.arguments as { request: UpdateCardRequest }).request;
      const updatedCard = await this.trelloClient.updateCard(card_id, update_data);
      return {
        content: [{ type: 'text', text: JSON.stringify(updatedCard, null, 2) }],
      };
    }
  • TypeScript interface defining the input structure for update_card: card_id and update_data.
    export interface UpdateCardRequest {
      card_id: string;
      update_data: Partial<Card>;
    }
  • src/index.ts:132-157 (registration)
    Tool registration in ListToolsRequestHandler, including name, description, and input schema matching UpdateCardRequest.
    {
      name: 'update_card',
      description: 'Update properties of a specific card',
      inputSchema: {
        type: 'object',
        properties: {
          request: {
            type: 'object',
            properties: {
              card_id: {
                type: 'string',
                description: 'ID of the card',
              },
              update_data: {
                type: 'object',
                description: 'Properties to update on the card',
                additionalProperties: true,
              },
            },
            required: ['card_id', 'update_data'],
          },
        },
        required: ['request'],
        title: 'update_cardArguments',
      },
    },
  • Core implementation of card update via Trello API using axios PUT request.
    async updateCard(cardId: string, updateData: Partial<Card>): Promise<Card> {
      const response = await axios.put(
        `${this.baseUrl}/cards/${cardId}?${this.getAuthParams()}`,
        updateData
      );
      return response.data;
    }
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. 'Update' implies a mutation, but it doesn't disclose behavioral traits like required permissions, whether changes are reversible, error handling, or rate limits. It lacks context beyond the basic action, leaving gaps for a mutation tool.

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 with zero waste. It's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration, earning its place as 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 the tool's complexity as a mutation with nested parameters, no annotations, no output schema, and 0% schema coverage, the description is incomplete. It doesn't explain what properties can be updated, the response format, or behavioral aspects, making it inadequate for safe and effective use by an AI agent.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'properties of a specific card,' which hints at parameters but doesn't detail card_id or update_data. With 1 parameter (a nested object) and no schema descriptions, the description adds minimal meaning beyond the schema, failing to address the coverage gap.

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 'Update properties of a specific card' clearly states the verb ('update') and resource ('specific card'), but it's vague about what properties can be updated and doesn't distinguish from sibling tools like get_card_details or get_cards. It provides a basic purpose but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, such as needing a card_id from get_cards or get_card_details, or clarify that this is for modifications while siblings are for retrieval. It offers no explicit when/when-not instructions.

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