Skip to main content
Glama
diegofornalha

MCP Server Trello

update_card_details

Modify card details on Trello, including name, description, due date, and labels, using the card ID for precise updates. Simplifies card management without manual intervention.

Instructions

Update an existing card's details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardIdYesID of the card to update
descriptionNoNew description for the card
dueDateNoNew due date for the card (ISO 8601 format)
labelsNoNew array of label IDs for the card
nameNoNew name for the card

Implementation Reference

  • Core implementation of updating card details via Trello API PUT request.
    async updateCard(params: {
      cardId: string;
      name?: string;
      description?: string;
      dueDate?: string;
      labels?: string[];
    }): Promise<TrelloCard> {
      return this.handleRequest(async () => {
        const response = await this.axiosInstance.put(`/cards/${params.cardId}`, {
          name: params.name,
          desc: params.description,
          due: params.dueDate,
          idLabels: params.labels,
        });
        return response.data;
      });
    }
  • MCP CallTool handler case for 'update_card_details' that validates and delegates to TrelloClient.
    case 'update_card_details': {
      const validArgs = validateUpdateCardRequest(args);
      const card = await this.trelloClient.updateCard(validArgs);
      return {
        content: [{ type: 'text', text: JSON.stringify(card, null, 2) }],
      };
    }
  • Input validation function for update_card_details tool parameters.
    export function validateUpdateCardRequest(args: Record<string, unknown>): {
      cardId: string;
      name?: string;
      description?: string;
      dueDate?: string;
      labels?: string[];
    } {
      if (!args.cardId) {
        throw new McpError(ErrorCode.InvalidParams, 'cardId is required');
      }
      return {
        cardId: validateString(args.cardId, 'cardId'),
        name: validateOptionalString(args.name),
        description: validateOptionalString(args.description),
        dueDate: validateOptionalString(args.dueDate),
        labels: validateOptionalStringArray(args.labels),
      };
    }
  • src/index.ts:131-163 (registration)
    Tool registration including name, description, and input schema for ListTools response.
    {
      name: 'update_card_details',
      description: 'Update an existing card\'s details',
      inputSchema: {
        type: 'object',
        properties: {
          cardId: {
            type: 'string',
            description: 'ID of the card to update',
          },
          name: {
            type: 'string',
            description: 'New name for the card',
          },
          description: {
            type: 'string',
            description: 'New description for the card',
          },
          dueDate: {
            type: 'string',
            description: 'New due date for the card (ISO 8601 format)',
          },
          labels: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'New array of label IDs for the card',
          },
        },
        required: ['cardId'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Update an existing card's details,' which implies a mutation operation, but fails to mention critical aspects like required permissions, whether updates are reversible, potential side effects (e.g., notifications), or rate limits. This leaves significant gaps for an agent to understand the tool's behavior safely.

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 any unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 complexity of a mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., permissions, side effects), usage context, and what the tool returns, leaving the agent with insufficient guidance for safe and effective invocation.

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?

The schema description coverage is 100%, with each parameter clearly documented in the input schema (e.g., 'cardId' as ID, 'dueDate' in ISO 8601 format). The description adds no additional meaning beyond what the schema provides, such as explaining relationships between parameters or usage examples. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('an existing card's details'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings like 'archive_card' or 'add_card_to_list' beyond the general 'update' action, which is why it doesn't reach a perfect score.

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. For example, it doesn't mention prerequisites (e.g., needing the card ID), when not to use it (e.g., for archiving vs. updating), or how it relates to siblings like 'archive_card' or 'get_cards_by_list_id' for retrieval before updating.

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

Related 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/diegofornalha/mcp-server-trello'

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