Skip to main content
Glama
agrath

Atlassian Trello MCP Server

trello_create_check_item

Add a check item to a Trello checklist with due date and member assignment. Supports position and checked state.

Instructions

Add an item to a checklist. Supports due dates and member assignment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyNoTrello API key (optional if TRELLO_API_KEY env var is set)
tokenNoTrello API token (optional if TRELLO_TOKEN env var is set)
checklistIdYesID of the checklist to add the item to
nameYesText of the check item
posNoPosition: "top", "bottom", or a number
checkedNoWhether the item should start as checked
dueNoDue date in ISO 8601 format (e.g., "2024-12-31T23:59:59Z")
idMemberNoID of the member to assign

Implementation Reference

  • Handler function that executes the 'trello_create_check_item' tool logic. Validates input, calls TrelloClient.createCheckItem(), and returns the created check item with rate limit info.
    export async function handleTrelloCreateCheckItem(args: unknown) {
      try {
        const { credentials, params } = extractCredentials(args);
        const { checklistId, name, pos, checked, due, idMember} = validateCreateCheckItem(params);
        const client = new TrelloClient(credentials);
    
        const response = await client.createCheckItem(checklistId, {
          name,
          ...(pos !== undefined && { pos }),
          ...(checked !== undefined && { checked }),
          ...(due && { due }),
          ...(idMember && { idMember })
        });
        const item = response.data;
    
        return {
          content: [{
            type: 'text' as const,
            text: JSON.stringify({
              summary: `Created check item "${item.name}"`,
              checkItem: {
                id: item.id,
                name: item.name,
                state: item.state,
                pos: item.pos,
                due: item.due,
                idMember: item.idMember
              },
              rateLimit: response.rateLimit
            }, null, 2)
          }]
        };
      } catch (error) {
        return handleToolError(error, 'creating check item');
      }
  • Zod validation schema for the create check item operation. Validates checklistId, name, pos, checked, due, and idMember fields.
    const validateCreateCheckItem = (args: unknown) => {
      const schema = z.object({
    
        checklistId: trelloIdSchema,
        name: z.string().min(1, 'Check item name is required'),
        pos: z.union([z.string(), z.number()]).optional(),
        checked: z.boolean().optional(),
        due: z.string().optional(),
        idMember: trelloIdSchema.optional()
      });
      return schema.parse(args);
    };
  • TypeScript interface for the create check item API request payload. Defines name, pos, checked, due, and idMember fields.
    export interface CreateCheckItemRequest {
      name: string;
      pos?: string | number;
      checked?: boolean;
      due?: string;
      idMember?: string;
    }
  • Tool definition with name 'trello_create_check_item', description, and inputSchema (OpenAPI-style). Used to register the tool with the MCP server.
    export const trelloCreateCheckItemTool: Tool = {
      name: 'trello_create_check_item',
      description: 'Add an item to a checklist. Supports due dates and member assignment.',
      inputSchema: {
        type: 'object',
        properties: {
          apiKey: { type: 'string', description: 'Trello API key (optional if TRELLO_API_KEY env var is set)' },
          token: { type: 'string', description: 'Trello API token (optional if TRELLO_TOKEN env var is set)' },
          checklistId: { type: 'string', description: 'ID of the checklist to add the item to' },
          name: { type: 'string', description: 'Text of the check item', minLength: 1 },
          pos: { oneOf: [{ type: 'string', enum: ['top', 'bottom'] }, { type: 'number', minimum: 0 }], description: 'Position: "top", "bottom", or a number' },
          checked: { type: 'boolean', description: 'Whether the item should start as checked', default: false },
          due: { type: 'string', description: 'Due date in ISO 8601 format (e.g., "2024-12-31T23:59:59Z")', format: 'date-time' },
          idMember: { type: 'string', description: 'ID of the member to assign' }
        },
        required: ['checklistId', 'name']
      }
    };
  • TrelloClient.createCheckItem() - Makes the actual HTTP POST request to Trello API /checklists/{checklistId}/checkItems to create a check item.
    async createCheckItem(checklistId: string, data: CreateCheckItemRequest): Promise<TrelloApiResponse<TrelloCheckItem>> {
      return this.makeRequest<TrelloCheckItem>(
        `/checklists/${checklistId}/checkItems`,
        {
          method: 'POST',
          body: JSON.stringify(data)
        },
        `Create check item "${data.name}" on checklist ${checklistId}`
      );
    }
Behavior3/5

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

No annotations are provided, so description bears the burden. It mentions support for due dates and member assignment, but lacks disclosure about error handling, side effects, or prerequisites beyond the schema.

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?

Extremely concise: one sentence with no wasted words. Every part adds value, especially noting optional features.

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 8 parameters, 2 required, and no output schema, the description is incomplete. It does not explain return values, error cases, or prerequisites beyond schema.

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 description adds little beyond the schema—'Supports due dates and member assignment' merely highlights existing fields.

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

Purpose5/5

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

The description clearly states 'Add an item to a checklist' with a specific verb and resource, distinguishing it from sibling tools like trello_create_checklist and trello_update_check_item.

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

Usage Guidelines3/5

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

The description implies usage by stating 'Add an item to a checklist', but does not provide explicit when/when-not context or mention alternative tools for updates or deletions.

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/agrath/Trello-Desktop-MCP'

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