Skip to main content
Glama
diegofornalha

MCP Server Trello

add_card_to_list

Create and add a new card to a specified list in Trello, including optional details like description, due date, and labels, for organized task management.

Instructions

Add a new card to a specified list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoDescription of the card
dueDateNoDue date for the card (ISO 8601 format)
labelsNoArray of label IDs to apply to the card
listIdYesID of the list to add the card to
nameYesName of the card

Implementation Reference

  • Core implementation of adding a card to a Trello list via API POST to /cards endpoint with listId, name, etc.
    async addCard(params: {
      listId: string;
      name: string;
      description?: string;
      dueDate?: string;
      labels?: string[];
    }): Promise<TrelloCard> {
      return this.handleRequest(async () => {
        const response = await this.axiosInstance.post('/cards', {
          idList: params.listId,
          name: params.name,
          desc: params.description,
          due: params.dueDate,
          idLabels: params.labels,
        });
        return response.data;
      });
    }
  • Input validation function for add_card_to_list tool parameters.
    export function validateAddCardRequest(args: Record<string, unknown>): {
      listId: string;
      name: string;
      description?: string;
      dueDate?: string;
      labels?: string[];
    } {
      if (!args.listId || !args.name) {
        throw new McpError(ErrorCode.InvalidParams, 'listId and name are required');
      }
      return {
        listId: validateString(args.listId, 'listId'),
        name: validateString(args.name, 'name'),
        description: validateOptionalString(args.description),
        dueDate: validateOptionalString(args.dueDate),
        labels: validateOptionalStringArray(args.labels),
      };
    }
  • src/index.ts:98-130 (registration)
    MCP tool registration including name, description, and input schema for 'add_card_to_list'.
    {
      name: 'add_card_to_list',
      description: 'Add a new card to a specified list',
      inputSchema: {
        type: 'object',
        properties: {
          listId: {
            type: 'string',
            description: 'ID of the list to add the card to',
          },
          name: {
            type: 'string',
            description: 'Name of the card',
          },
          description: {
            type: 'string',
            description: 'Description of the card',
          },
          dueDate: {
            type: 'string',
            description: 'Due date for the card (ISO 8601 format)',
          },
          labels: {
            type: 'array',
            items: {
              type: 'string',
            },
            description: 'Array of label IDs to apply to the card',
          },
        },
        required: ['listId', 'name'],
      },
    },
  • MCP CallToolRequest handler case that validates input, calls TrelloClient.addCard, and formats response.
    case 'add_card_to_list': {
      const validArgs = validateAddCardRequest(args);
      const card = await this.trelloClient.addCard(validArgs);
      return {
        content: [{ type: 'text', text: JSON.stringify(card, null, 2) }],
      };
    }
  • Type definition for TrelloCard, used as return type for addCard operation.
    export interface TrelloCard {
      id: string;
      name: string;
      desc: string;
      due: string | null;
      idList: string;
      idLabels: string[];
      closed: boolean;
      url: string;
      dateLastActivity: string;
    }
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 the tool adds a card but lacks details on permissions required, whether the operation is idempotent, error handling, or what happens on success (e.g., returns a card ID). This is a significant gap for a mutation tool with zero 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 with zero waste—it directly states the tool's purpose without fluff or redundancy. It's appropriately sized and front-loaded, making it easy 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 no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects, return values, or error conditions, which are critical for an agent to use this tool effectively in context with its siblings.

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 5 parameters thoroughly. The description adds no parameter-specific information beyond what the schema provides, such as explaining relationships between fields or usage tips. Baseline 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 action ('Add a new card') and target resource ('to a specified list'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'update_card_details' or 'archive_card' beyond the basic verb, missing explicit distinction in scope or purpose.

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 prerequisites (e.g., needing a list ID), exclusions, or comparisons to siblings like 'update_card_details' for modifying existing cards or 'get_cards_by_list_id' for retrieval, leaving usage context implied at best.

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