Skip to main content
Glama

create_card

Adds a new card to a specified Trello list, letting you set its name, description, due date, labels, members, and position for organized task tracking.

Instructions

Create a card in a list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listId": "<listId>",
      "name": "<name>"
    },
    "name": "create_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoISO 8601 date
posNotop, bottom, or a number
descNo
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
nameYes
startNoStart date, ISO 8601
listIdYes
idLabelsNoComma-separated label ids
idMembersNoComma-separated member ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, but the description adds nothing beyond them. It does not say what position a new card takes by default, whether it mutates the list's ordering, or what permissions are needed for a mutation on an open-world server.

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?

One short, front-loaded clause with zero filler, which is easy to scan. Its brevity comes at the cost of substance rather than containing wasted wording.

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?

For a 9-parameter mutation tool with no output schema, this description is far too thin. It omits required fields, defaults for ordering, and side effects, so the agent must rely entirely on the partially documented schema.

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

Parameters2/5

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

With 9 parameters and only 67% schema description coverage, name, desc, and listId have no schema documentation at all, and the description does not compensate. It never mentions that listId and name are required or what any of the optional fields do.

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?

"Create a card in a list" gives a specific verb (create) and resource (card) plus its container, so the agent knows the effect. It does not distinguish this from siblings such as copy_card or create_list, leaving that inference to the agent.

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 versus copy_card or update_card, and no statement of prerequisites such as needing an existing listId. The agent must infer both the situation and the preconditions from the parameter names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.