Skip to main content
Glama

create-cards

Add multiple cards to Trello lists with names, descriptions, and list assignments to organize tasks and projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardsYes

Implementation Reference

  • The async handler function implementing the 'create_card' MCP tool. It retrieves the CardService from ServiceFactory and calls createCard with the tool arguments.
    /**
     * Create a new card
     * @param args - Tool arguments
     * @returns Promise resolving to the created card
     */
    create_card: async (args: any) => {
        const cardService = ServiceFactory.getInstance().getCardService();
        return cardService.createCard(args);
    },
  • The JSON schema definition and metadata for the 'create_card' tool, including input parameters and requirements.
    name: "create_card",
    description: "Create a new card on a list. Use this tool when you need to add a new card to a list.",
    inputSchema: {
        type: "object",
        properties: {
            name: {
                type: "string",
                description: "Name of the card"
            },
            idList: {
                type: "string",
                description: "ID of the list the card should belong to"
            },
            desc: {
                type: "string",
                description: "Description of the card"
            },
            pos: {
                type: ["string", "number"],
                description: "Position of the card (top, bottom, or a positive number)"
            },
            due: {
                type: ["string", "null"],
                description: "Due date for the card (ISO-8601 format, e.g., 2023-12-31T12:00:00Z)"
            },
            start: {
                type: ["string", "null"],
                description: "Start date for the card (ISO-8601 format, e.g., 2023-12-31T12:00:00Z)"
            },
            dueComplete: {
                type: "boolean",
                description: "Whether the due date is complete"
            },
            idMembers: {
                type: "array",
                items: { type: "string" },
                description: "IDs of members to assign to the card"
            },
            idLabels: {
                type: "array",
                items: { type: "string" },
                description: "IDs of labels to add to the card"
            },
            urlSource: {
                type: "string",
                description: "URL to attach to the card"
            },
            idCardSource: {
                type: "string",
                description: "ID of a card to copy from"
            },
            keepFromSource: {
                type: "string",
                description: "What to copy from the source card (all or a comma-separated list of: attachments, checklists, comments, due, labels, members, stickers)"
            },
            address: {
                type: "string",
                description: "Address for the card"
            },
            locationName: {
                type: "string",
                description: "Location name for the card"
            },
            coordinates: {
                type: "string",
                description: "Coordinates for the card (latitude,longitude)"
            }
        },
        required: ["name", "idList"]
    }
  • src/index.ts:97-101 (registration)
    MCP server registration for the ListToolsRequestSchema, which exposes the 'create_card' tool schema as part of trelloTools.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
        return {
            tools: trelloTools
        };
    });
  • src/index.ts:125-142 (registration)
    MCP server registration for CallToolRequestSchema, which dispatches to the 'create_card' handler from trelloToolHandlers based on tool name.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
        try {
            const toolName = request.params.name;
            // Use type assertion to tell TypeScript that toolName is a valid key
            const handler = trelloToolHandlers[toolName as keyof typeof trelloToolHandlers];
    
            if (!handler) {
                throw new McpError(
                    ErrorCode.MethodNotFound,
                    `Unknown tool: ${toolName}`
                );
            }
    
            // Execute the tool handler with the provided arguments
            const result = await handler(request.params.arguments);
    
            // Return the result
            return {
  • Aggregation of all tool schemas into trelloTools array, spreading cardTools which includes 'create_card'.
    export const trelloTools = [
        ...boardTools,
        ...listTools,
        ...cardTools,
        ...memberTools,
        ...labelTools,
        ...checklistTools
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

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