Skip to main content
Glama
stefanoverna

Basecamp MCP Server

by stefanoverna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Basecamp Message

basecamp_update_message

Update a Basecamp message by replacing its subject or content, or by applying append, prepend, and search-replace edits.

Instructions

Update a message. 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
contentNoIf provided, replaces entire HTML content. Cannot be used with content_append, content_prepend, or search_replace.
subjectNoNew message subject
message_idYesBasecamp resource identifier
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.
message_type_idNoOptional message type/category ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.2.1
    • removedInput schema / properties / bucket_id
      Removed value: -{
-  "description": "Basecamp resource identifier",
-  "type": "number"
-}
    • removedInput schema / properties / message_id / $ref
      Removed value: -"#/properties/bucket_id"
    • addedInput schema / properties / message_id / description
      Added value: +"Basecamp resource identifier"
    • addedInput schema / properties / message_id / type
      Added value: +"number"
    • changedInput schema / properties / message_type_id / $ref
      Previous value: -"#/properties/bucket_id"New value: +"#/properties/message_id"
    • changedInput schema / required
      Previous value: -[
-  "bucket_id",
-  "message_id"
-]New value: +[
+  "message_id"
+]
  2. Addedv1.0.0

TDQS

A4.2/5.0
Behavior5/5

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

The description goes far beyond the annotations, explaining that Basecamp auto-enriches bc-attachment tags after saving, that existing enriched tags are collapsed back to minimal form before partial operations, and exactly which tags/styling are allowed. Even though annotations already carry the mutation profile (readOnlyHint=false, destructiveHint=false), this content-rich behavioral context is genuinely additive.

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 the multiple HTML and attachment rules are information-dense and necessary for correct invocation. It is front-loaded with the token-saving tip and uses clear bullets for the rule sharkline; little is wasted.

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 7 parameters, no entire-notes structure, and no output schema, the description does the heavy lifting: HTML syntax, highlight values, attachment handling, and idempotency. Gaps such as the response format and permission requirements exist, but the core calling contract is well covered.

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 100%, so the baseline is 3. The description adds real parameter semantics beyond the schema by explaining how content, content_append, content_prepend, and search_replace interrelate and how attachment content behaves in each case. It doesn't document every parameter in prose, but the schema already does that.

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?

"Update a message" states a specific verb and resource, and the sentence about partial content operations clarifies the scope of the tool. It doesn't explicitly differentiate the tool from siblings like basecamp_update_comment or basecamp_update_document, but the verb-resource pairing and title make the target 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 gives concrete usage guidance: prefer partial operations (append/prepend/search_replace) over full content replacement when possible to save tokens. It does not spell out when to choose this tool over an alternative like basecamp_create_message, but the guidance within the tool's own operation modes is clear and actionable.

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