Skip to main content
Glama

Create a card

create_card

Create a new card in a Trello list by specifying its name, description, due date, position, members, or labels.

Instructions

Create a new card in a list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dueNoDue date as ISO 8601 (e.g. 2026-07-01T17:00:00Z)
posNoPosition: "top", "bottom", or a positive number
descNoCard description (markdown)
nameYesCard name/title
idListNoList id to create the card in (defaults to TRELLO_LIST_ID if set)
idLabelsNoLabel ids to apply
idMembersNoMember ids to assign
Behavior2/5

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

No annotations present, so description must fully disclose behavior. Only states basic create action, with no mention of side effects, permissions, rate limits, or idempotency.

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?

Extremely concise (7 words), which is efficient. However, lacks structure such as bullet points or sections to improve readability.

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?

No output schema, so return value is unexplained. Description omits usage context, default behavior for optional parameters, and potential errors.

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 schema already documents all parameters. Description adds no additional meaning beyond what is in the schema.

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?

Description clearly states 'Create a new card in a list' with a specific verb and resource. However, it does not differentiate from sibling tools like 'update_card' or 'add_card_member', which could cause confusion for similar operations.

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 such as 'update_card' or 'add_card_member'. No prerequisites or context provided.

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

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