Skip to main content
Glama

update_board_card

Idempotent

Update board card fields: title, description, status, assignee, members, location, cover, start date, and due date. Use null to clear specific fields.

Instructions

Update board card fields: title, markdown description, status, assignee, members, location, cover, startDate, and dueDate. Use null to clear clearable fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardYesa string that will be trimmed
cardYesa string that will be trimmed
titleNoa string that will be trimmed
descriptionNoNew board card description in markdown. Pass null to clear; empty string is also accepted.
statusNoa string that will be trimmed
assigneeNoNew assignee Employee _id, exact email, or exact person display name; null unassigns.
membersNoReplace card members with this exact list. Cannot be combined with addMembers or removeMembers.
addMembersNoMembers to add without replacing existing members.
removeMembersNoMembers to remove without replacing existing members.
locationNoNew card location. Pass null to clear; empty string is also accepted.
coverNoNew card cover; null clears the cover.
startDateNoNew start date timestamp in milliseconds; null clears it.
dueDateNoNew due date timestamp in milliseconds; null clears it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior4/5

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

Annotations indicate non-read-only, non-destructive, idempotent. Description adds clearing behavior with null, which is valuable. No mention of auth or side effects, but output schema covers return values.

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?

Two sentences with no wasted words. Front-loaded with action and list of fields. Could be slightly more structured but is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 13 parameters, the description covers the main updatable fields and clearing behavior. It doesn't detail members/addMembers/removeMembers distinction, but schema handles that. Generally complete.

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 coverage is 100%, so baseline is 3. Description lists fields but adds little beyond schema descriptions. The null clearing note is generic and already partially in schema.

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 the verb 'Update' and the resource 'board card', listing specific fields (title, description, status, etc.). It distinguishes from siblings like create_board_card or delete_board_card.

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

Usage Guidelines4/5

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

Provides explicit guidance on using null to clear clearable fields, which is useful. However, it does not mention when not to use this tool or suggest alternatives, though the tool name and sibling list imply uniqueness.

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/dearlordylord/huly-mcp'

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