Skip to main content
Glama
stefanoverna

Basecamp MCP Server

by stefanoverna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Basecamp Todo

basecamp_update_todo
Idempotent

Update a todo item in Basecamp by modifying its title, dates, assignees, or content using partial updates to save tokens.

Instructions

Update a todo item. Use partial content operations when possible to save on token usage.

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.

  • Use for paragraphs. Use for empty line spacing between paragraphs.

  • Headings: use , , as appropriate.

  • Inline code: text. Preformatted blocks: text.

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

  • Tables: Heading...Cell...

  • To mention people:

  • Single image:

  • Image gallery: wrap multiple in a .

  • 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
titleNoNew todo title
due_onNoDue date in YYYY-MM-DD format. Pass an empty string to clear the due date.
notifyNoWhether to notify the assignees about this todo
contentNoIf provided, replaces entire HTML content. Cannot be used with content_append, content_prepend, or search_replace.
todo_idYesBasecamp resource identifier
starts_onNoStart date in YYYY-MM-DD format (for a date range; requires due_on). Pass an empty string to clear it.
assignee_idsNoArray of person IDs to assign to this todo
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. Changed9 schema fields changedv1.2.1
    • changedInput schema / properties / assignee_ids / items / $ref
      Previous value: -"#/properties/bucket_id"New value: +"#/properties/todo_id"
    • removedInput schema / properties / bucket_id
      Removed value: -{
-  "description": "Basecamp resource identifier",
-  "type": "number"
-}
    • addedInput schema / properties / due_on
      Added value: +{
+  "description": "Due date in YYYY-MM-DD format. Pass an empty string to clear the due date.",
+  "pattern": "^(\\d{4}-\\d{2}-\\d{2})?$",
+  "type": "string"
+}
    • addedInput schema / properties / notify
      Added value: +{
+  "description": "Whether to notify the assignees about this todo",
+  "type": "boolean"
+}
    • addedInput schema / properties / starts_on
      Added value: +{
+  "$ref": "#/properties/due_on",
+  "description": "Start date in YYYY-MM-DD format (for a date range; requires due_on). Pass an empty string to clear it."
+}
    • removedInput schema / properties / todo_id / $ref
      Removed value: -"#/properties/bucket_id"
    • addedInput schema / properties / todo_id / description
      Added value: +"Basecamp resource identifier"
    • addedInput schema / properties / todo_id / type
      Added value: +"number"
    • changedInput schema / required
      Previous value: -[
-  "bucket_id",
-  "todo_id"
-]New value: +[
+  "todo_id"
+]
  2. Addedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

The description adds meaningful behavioral details beyond the annotations, such as how bc-attachment tags are auto-enriched and how content operations automatically collapse enriched tags. It does not contradict the annotations, which mark the tool as non-readonly, non-destructive, and idempotent.

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?

The description is long but appropriately so, given the complex HTML formatting rules for Basecamp content. It is front-loaded with the purpose, followed by practical usage guidance. The structure is logical, though the sheer volume of formatting rules makes it less concise than ideal.

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?

The description covers the tool's purpose, content editing strategies, and detailed HTML requirements, which is sufficient for the tool's complexity. It does not mention return values, but there is no output schema and the focus is on the action, so this is not a significant gap.

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?

The input schema already provides 100% parameter coverage with clear descriptions. The description adds extra semantic value by explaining HTML content rules and advising when to use content_append/content_prepend/search_replace instead of content, which enhances understanding of the content-related parameters.

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 todo item', giving a specific verb and resource. It distinguishes this from sibling tools like update_comment, update_message, and update_document without ambiguity.

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?

The description provides useful guidance on using partial content operations to save tokens and includes extensive HTML formatting rules. However, it does not explicitly explain when to choose this tool over alternatives such as complete_todo or uncomplete_todo, so usage context is only partially implied.

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

Deploy Server

Other Tools