Skip to main content
Glama

update_card

Update a card's properties including name, board, lane, description, tasks, checklists, custom fields, and archive status in Favro.

Instructions

Update a card's properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cardYesCard ID, sequential ID (#123), or name
laneNoLane (swimlane) ID or name to move the card into. Only applies to boards with lanes enabled; use list_lanes to see available lanes.
nameNoNew card name
boardNoBoard ID or name (needed for sequential ID or name lookup)
tasksNoList of task updates. Each dict should contain 'task_id' and optionally 'completed' (bool) or 'name' (str) to update
add_taskNoAdd a task (checkbox item) to an existing tasklist: {'tasklist_id': '...', 'name': '...'}
archivedNoArchive or unarchive the card
descriptionNoNew detailed 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 the add_tasklist and add_task parameters instead.
add_tasklistNoCreate a new checklist on this card with this name. This is how checklists work in Favro — they are tasklists, not markdown checkboxes in the description. Returns the tasklist_id needed for add_task.
custom_fieldsNoList of custom field updates. Each dict should contain 'customFieldId' and the appropriate value field for the field type: - Text: {'customFieldId': '...', 'value': 'text'} - Number/Rating: {'customFieldId': '...', 'total': 5} - Link: {'customFieldId': '...', 'link': {'url': '...', 'text': '...'}} - Checkbox: {'customFieldId': '...', 'value': True} - Date: {'customFieldId': '...', 'value': '2024-01-15'} - Status: {'customFieldId': '...', 'value': ['itemId1', 'itemId2']}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure, but it only says 'Update a card's properties.' It does not mention potential side effects, required permissions, or limitations such as rate limits or field constraints.

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

Conciseness3/5

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

The description is extremely concise (one short sentence), but lacks structure and fails to provide necessary context. It is not front-loaded with key information; it is just a minimal statement.

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 has 10 parameters and no annotations, the description is far too brief. It does not explain the overall behavior, return values (though output schema exists), or prerequisites, leaving many gaps.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for parameters.

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 verb (update) and resource (card), indicating it modifies card properties. However, it lacks differentiation from sibling tools like assign_card or tag_card, which also modify cards.

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 vs alternatives. The description does not specify conditions, prerequisites, or scenarios where this tool is preferred over other card-modifying tools.

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