Skip to main content
Glama

create_card

Add a new card to a Favro board by specifying its name and optional details like board, column, description, tags, and assignees.

Instructions

Create a new card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCard name/title
boardNoBoard ID or name (uses current board if not specified)
columnNoColumn ID or name to place the card in
descriptionNoDetailed description. Favro supports a subset of Markdown: **bold**, *italic*, ~~strikethrough~~, `inline code`, ```code blocks```, [links](url), bullet lists, numbered lists, headings (# and ## only), and horizontal rules (---). Do not use tables, images, blockquotes, checkbox lists, or heading levels beyond ## — unsupported syntax causes the entire description to be stored as plain text. For checklists, use tasklists instead (see update_card's add_tasklist and add_task parameters).
tagsNoList of tag IDs or names to add
assigneesNoList of user IDs, names, or emails to assign

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

The description provides no behavioral details beyond the action. It does not disclose whether the operation is safe, what side effects occur (e.g., creation in current board), authorization requirements, or error conditions. With no annotations, the description fails to convey critical behavioral traits.

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

Conciseness2/5

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

At four words, the description is too terse for a tool with six parameters and complex behavior. It lacks structure and does not front-load key information. While brevity is valued, here it omits necessary context, making it under-specified rather than concise.

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 tool's complexity (6 parameters, output schema present), the description is incomplete. It does not explain the return value, how the card is created (e.g., which board/column), or any constraints. Even with an output schema, the description should provide more context to help the agent understand the tool's role.

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?

The input schema has 100% description coverage, meaning each parameter is already well-documented in the schema. The description adds no additional meaning beyond what the schema provides, so it meets the baseline for high coverage.

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 ('card'). While it is specific, it does not differentiate from sibling tools like update_card or delete_card, which also operate on cards. However, the verb 'create' is distinct enough for basic understanding.

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 is provided on when to use this tool versus alternatives (e.g., when to create via API vs other methods). There is no indication of prerequisites, such as needing a board or column context, or when not to use this tool.

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/truls27a/favro-mcp'

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