Skip to main content
Glama

Update Basecamp Todo

basecamp_update_todo
Idempotent

Update Basecamp todo items with title, assignment, or content modifications. Use partial content operations like append, prepend, or search-and-replace to minimize token usage while applying changes.

Instructions

Update a todo item. 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
todo_idYes
titleNoNew todo title
assignee_idsNoArray of person IDs to assign to this todo
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.
Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=false, but the description adds significant behavioral context: explains partial update mechanisms (search_replace, append/prepend), mutual exclusivity of content fields, and HTML formatting rules including allowed tags and color highlight syntax. This goes beyond annotations and helps the agent understand how the tool behaves.

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?

Front-loaded with main purpose and token-saving advice. The detailed HTML rules are necessary for correct use and well-organized. Though long, every part serves a function; no fluff.

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

Completeness3/5

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

Covers input side thoroughly with parameter semantics and usage tips. However, lacks explanation of what the tool returns or any side effects after update. No output schema exists, so description should ideally mention response format. Leaves some gaps for the agent.

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?

Input schema covers 88% of parameters with descriptions, but the description adds crucial context for content-related parameters: HTML formatting rules, how to mention people via bc-attachment with sgid, and the mutual exclusivity of content operations. This adds meaning beyond raw schema definitions.

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?

Clearly states 'Update a todo item' with specific verb and resource. Mentions partial content operations for token savings, which adds specificity. Does not explicitly distinguish from sibling tools like basecamp_complete_todo or basecamp_create_todo, but the name and context make it clear this is for updating existing todos.

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

Usage Guidelines3/5

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

Provides guidance on using partial content operations to save tokens, and details HTML formatting rules. However, it does not specify when NOT to use this tool or compare it to alternatives like create_todo or complete_todo. The advice is partial.

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