Skip to main content
Glama

Update Basecamp Todo List

basecamp_update_todolist
Idempotent

Rename a Basecamp todo list or section, or edit its HTML description using full replacement or partial append, prepend, and search-replace operations.

Instructions

Update the name or the description of a todo list, or of a group (section) in a todo list. Use partial content operations on the description when possible to save on token usage. A todo list is complete when all its todos are complete, so this tool cannot complete it.

HTML rules for content:

  • Allowed tags: p, span, h2, h3, h4, br, strong, em, strike, code, a (with href attribute), pre, ol, ul, li, blockquote, mark, figure, figcaption, table, tbody, tr, th, td, div, bc-attachment.

  • Wrap every paragraph in ..., and put between one paragraph and the next. Both parts are necessary: newlines and blank lines in your HTML are discarded, and Basecamp shows no space around a on its own, so two paragraphs with nothing between them are shown as one block of text. Do not rely on line breaks in your HTML to separate paragraphs.

  • Headings: use , , as appropriate.

  • Inline code: text. Preformatted blocks: text.

  • Ordered lists: .... Unordered: ....

  • Tables: Heading...Cell...

  • To mention a person: . Put the tag where the name must show in the text, for example "Thanks for the fix". The person gets a notification. If the ID is not a person, the tool returns an error and writes nothing. Get person IDs from basecamp_list_people, or from the people in other responses (assignees, creators).

  • Single image:

  • Image gallery: wrap multiple in a .

  • A bc-attachment needs an attachable_sgid. For a file that is already in Basecamp, take the sgid from the HTML content of the message, comment or card that shows it, or use basecamp_list_recordings. For a file that is not in Basecamp yet, such as an image at an external URL or a screenshot on disk, upload it with basecamp_create_attachment and use the sgid that it returns. There is no tag, so an external image URL can never be embedded directly: upload it, or accept that it stays a plain link.

  • Basecamp auto-enriches bc-attachment tags after saving (adds url, href, filename, content-type, etc.) — you never need to write those.

  • When you see an existing, already-enriched tag (e.g. from a previous list/get call), leave its inner HTML alone. Before any content_append/content_prepend/search_replace runs, it is automatically collapsed back to its minimal form (sgid, presentation, caption, and content-type for mentions) — you don't need to strip it yourself, and doing so manually is unnecessary and risks mismatched find strings.

  • Background highlights: ...

  • Text color highlights: ...

  • For both, N is 1 (yellow), 2 (amber), 3 (red), 4 (pink), 5 (purple), 6 (blue), 7 (teal), 8 (near-white), or 9 (light gray).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name
contentNoIf provided, replaces entire HTML content. Cannot be used with content_append, content_prepend, or search_replace.
todolist_idYesID of the todo list or group
content_appendNoText to append to the end of current content. Cannot be used with content.
search_replaceNoArray of search-replace operations to apply to current content. Cannot be used with content.
content_prependNoText to prepend to the beginning of current content. Cannot be used with content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: person mentions trigger notifications, an invalid person ID makes the whole write fail atomically, bc-attachment tags are auto-enriched on save and auto-collapsed before partial ops, and external images must be uploaded first (no <img> support). These side-effect and error semantics are exactly what the description should carry on top of readOnly=false/idempotent=true.

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?

Purpose is front-loaded and the HTML rules are bulleted, but the description is a very long wall of reference text with some redundancy ('you never need to write those', 'you don't need to strip it yourself yourself'). Most rules are load-bearing for correctness, yet the sheer length and overlap keep it from being tight.

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 mutation tool with no output schema, it comprehensively covers content formatting, error behavior, and attachment handling, which is what an agent needs to call it without producing malformed content. It stops short of describing the response shape or any permission/auth requirements.

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 already 100%, so the baseline is 3, but the description adds real semantics for content: the accepted HTML tag set, paragraph/heading/list/table conventions, mention and attachment syntax, and the token-saving rationale for append/prepend/search_replace. It goes beyond restating the schema fields.

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 opening sentence names a specific verb (Update) and resource (a todo list, or a group/section within it), and explicitly bounds scope by stating fields updated (name, description). It also distinguishes itself from completion-capable siblings with 'A todo list is complete when all its todos are complete, so this tool cannot complete it.' An agent can tell this apart from basecamp_update_todo, basecamp_complete_todo, and basecamp_move_todolist.

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?

Gives clear operational guidance: prefer partial content operations (append/prepend/search_replace) over full replacement to save tokens, and warns that any invalid person ID causes the tool to write nothing. It does not explicitly route the agent between this tool and alternatives like basecamp_move_todolist or basecamp_create_todolist_group, so it stops short of full when/when-not framing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.