Skip to main content
Glama

create_card

Add a new task to a Focalboard project board by specifying its title, properties, description, and column placement.

Instructions

Create a new card (task) in a board. You can set the title, properties, description, and column placement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesThe ID of the board to create the card in
titleYesThe title/name of the card
propertiesNoProperty values for the card (e.g., {"Status": "To Do", "Priority": "High"}). Use property names, not IDs.
descriptionNoOptional description/content for the card in markdown format

Implementation Reference

  • The primary handler for executing the 'create_card' MCP tool. Validates inputs, creates a basic card, optionally applies properties and description, then returns the resulting card JSON.
    case 'create_card': {
      const boardId = args?.boardId as string;
      const title = args?.title as string;
      const properties = (args?.properties as Record<string, string>) || {};
      const description = args?.description as string | undefined;
    
      if (!boardId || !title) {
        throw new Error('boardId and title are required');
      }
    
      // Create the card first
      const cardData: any = {
        title,
        fields: {
          properties: {},
          contentOrder: []
        }
      };
    
      let card = await focalboard.createCard(boardId, cardData);
    
      // If properties are provided, update the card with them
      if (Object.keys(properties).length > 0) {
        card = await focalboard.updateCardProperties(card.id, boardId, properties);
      }
    
      // If description is provided, add it as a text block
      if (description) {
        await focalboard.createTextBlock(boardId, card.id, description);
        // Refresh card to get updated contentOrder
        card = await focalboard.getCard(card.id);
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(card, null, 2)
          }
        ]
      };
    }
  • src/index.ts:79-107 (registration)
    Registration of the 'create_card' tool in the MCP tools list, including description and input schema definition.
    {
      name: 'create_card',
      description: 'Create a new card (task) in a board. You can set the title, properties, description, and column placement.',
      inputSchema: {
        type: 'object',
        properties: {
          boardId: {
            type: 'string',
            description: 'The ID of the board to create the card in'
          },
          title: {
            type: 'string',
            description: 'The title/name of the card'
          },
          properties: {
            type: 'object',
            description: 'Property values for the card (e.g., {"Status": "To Do", "Priority": "High"}). Use property names, not IDs.',
            additionalProperties: {
              type: 'string'
            }
          },
          description: {
            type: 'string',
            description: 'Optional description/content for the card in markdown format'
          }
        },
        required: ['boardId', 'title']
      }
    },
  • JSON schema defining the input parameters for the 'create_card' tool.
    inputSchema: {
      type: 'object',
      properties: {
        boardId: {
          type: 'string',
          description: 'The ID of the board to create the card in'
        },
        title: {
          type: 'string',
          description: 'The title/name of the card'
        },
        properties: {
          type: 'object',
          description: 'Property values for the card (e.g., {"Status": "To Do", "Priority": "High"}). Use property names, not IDs.',
          additionalProperties: {
            type: 'string'
          }
        },
        description: {
          type: 'string',
          description: 'Optional description/content for the card in markdown format'
        }
      },
      required: ['boardId', 'title']
  • Helper method in FocalboardClient that implements the core card creation logic by making a POST request to the Focalboard API endpoint `/boards/{boardId}/blocks`.
    async createCard(boardId: string, card: Partial<Card>): Promise<Card> {
      const newCard = {
        boardId,
        parentId: card.parentId || boardId,
        type: 'card',
        schema: 1,
        title: card.title || '',
        fields: card.fields || {
          properties: {},
          contentOrder: [],
          icon: '',
          isTemplate: false
        },
        createAt: Date.now(),
        updateAt: Date.now(),
        deleteAt: 0,
        createdBy: '',
        modifiedBy: '',
        limited: false
      };
    
      // The /blocks endpoint expects an array and returns an array
      const createdCards = await this.makeRequest<Card[]>(
        `/boards/${boardId}/blocks`,
        'POST',
        [newCard]
      );
    
      // Return the first (and only) created card
      return createdCards[0];
    }
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. It mentions the action ('Create') but doesn't disclose behavioral traits like required permissions, whether the operation is idempotent, error handling, or what happens on success (e.g., returns a card ID). This leaves significant 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.

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the main purpose and lists key settable attributes. It avoids redundancy and wastes no words, though it could be slightly more structured for clarity.

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 (mutation tool with 4 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral aspects like permissions, return values, or error conditions, which are crucial for proper tool invocation by an AI agent.

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 fully documents all parameters. The description adds minimal value by listing what can be set (title, properties, description, column placement), but doesn't provide additional semantics beyond the schema, such as format details for 'column placement' not covered in the schema. Baseline 3 is appropriate.

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 ('Create a new card') and resource ('in a board'), with additional details about what can be set (title, properties, description, column placement). It distinguishes from siblings like 'add_card_description' or 'update_card' by focusing on creation, though it doesn't explicitly contrast with them.

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 on when to use this tool versus alternatives like 'update_card' or 'add_card_description' is provided. The description implies usage for creating new cards but lacks context about prerequisites, such as needing a valid boardId, or exclusions, such as not using it for modifying existing cards.

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/gmjuhasz/focalboard-mcp-server'

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