Skip to main content
Glama

Update Kanban Card

basecamp_update_kanban_card

Update a kanban card's title, content, due date, assignees, and steps. Supports partial content edits via append, prepend, or search-replace to reduce token usage.

Instructions

Update a kanban card including its steps. At least one field (title, content, partial content operations, or steps) must be provided. Use partial content operations when possible to save on token usage.

HTML rules for content:

  • Allowed tags: div, span, h1, br, strong, em, strike, a (with an href attribute), pre, ol, ul, li, blockquote, bc-attachment (with sgid attribute).

  • Try to be semantic despite the limitations of tags. Use double to create paragraph spacing

  • To mention people:

  • To consume less tokens, existing tags can be rewritten by dropping any attributes/inner content and just leave the "sgid" and "caption" attributes, without loosing any information

  • You can highlight parts of the content in this format ... valid colors are:

    • red: 255, 229, 229

    • yellow: 250, 247, 133

    • green: 228, 248, 226

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucket_idYesBasecamp resource identifier
card_idYes
titleNoNew card title
contentNoIf provided, replaces entire HTML content. Cannot be used with content_append, content_prepend, or search_replace.
content_appendNoText to append to the end of current content. Cannot be used with content.
content_prependNoText to prepend to the beginning of current content. Cannot be used with content.
search_replaceNoArray of search-replace operations to apply to current content. Cannot be used with content.
due_onNoDue date (YYYY-MM-DD format) or null to clear
notifyNoWhether to notify assignees of the update
assignee_idsNoArray of user IDs to assign to the card
stepsNoComplete array of desired steps. Array order defines position. Steps not in array will be deleted.
Behavior4/5

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

The description discloses key behaviors: steps not in the array are deleted, partial content operations are preferred, and HTML rules are detailed. Annotations (readOnlyHint=false, destructiveHint=false) align with mutation without destruction. The openWorldHint=true is not addressed, but the description covers the most common side effects.

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 front-loaded with the purpose and requirement, but the HTML rules section is lengthy and detailed. While necessary for correct usage, it reduces conciseness. The structure is logical but could be more compact.

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?

Given the tool's complexity (11 parameters, nested steps), the description covers essential aspects: required fields, partial content operations, step deletion behavior, and HTML formatting. Return values are not described (no output schema), but that is acceptable. Missing explanation of openWorldHint implications, but overall sufficiently complete.

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

Parameters4/5

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

Schema coverage is high (91%), and the description adds value beyond schema by recommending partial content operations for token efficiency and detailing HTML rules for content fields. This helps the agent produce correct formatting beyond what the schema constraints convey.

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 'Update a kanban card including its steps.' and lists updatable fields, distinguishing it from sibling tools like basecamp_move_kanban_card and basecamp_create_kanban_card. The verb 'update' is specific to modification, and 'kanban card' is the resource, making the purpose unambiguous.

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?

The description explicitly requires at least one field to be provided and recommends using partial content operations to save token usage. However, it does not explicitly state when to avoid this tool or compare it to alternatives like basecamp_update_todo. The guidance on partial operations is helpful but lacks exclusions.

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/stefanoverna/basecamp-mcp'

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