Skip to main content
Glama
stefanoverna

Basecamp MCP Server

by stefanoverna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Basecamp Comment

basecamp_update_comment

Update a Basecamp comment by replacing its full HTML or using partial append, prepend, and search-replace operations to edit only what changed.

Instructions

Update a comment. 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.

  • 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
contentNoIf provided, replaces entire HTML content. Cannot be used with content_append, content_prepend, or search_replace.
comment_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.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (destructiveHint=false, idempotentHint=false, openWorldHint=true), so the description is free to add context — and it does: mentions trigger notifications, an invalid person ID "returns an error and writes nothing," and bc-attachment tags are auto-enriched on save and auto-collapsed before content operations run. This is meaningful behavior beyond the annotations, though permission/ownership constraints are unmentioned.

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 purpose and the partial-operation tip are front-loaded, and the HTML reference is broken into scannable bullets rather than prose. It is long, but nearly every bullet carries a rule required for a valid call (paragraph wrapping, mention syntax, attachment sgid sourcing), so the size is largely earned.

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 rich-content mutation tool with no output schema, the definition supplies the formatting contract, the mention/attachment mechanics, and error behavior, which is the hard part of calling this correctly. It stops short of describing the return payload and any permission or existence requirements for comment_id, leaving small gaps.

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 three exclusive modes (content vs content_append/content_prepend/search_replace) are already documented in the schema, giving a baseline of 3. The description earns above baseline by adding a preference rule for partial operations and, critically, by specifying the HTML dialect that the `content` string must conform to — semantics the schema cannot express.

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?

The first sentence gives a clear verb+resource ("Update a comment"), which is self-evident against the update/create family of siblings. However, it never explicitly contrasts with the closely related basecamp_create_comment or basecamp_list_comments, so sibling differentiation relies on the reader's inference from the verb alone.

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?

"Use partial content operations when possible to save on token usage" is genuine guidance on which parameter mode to prefer, and the HTML rules implicitly define the expected input context. But there is no explicit when-to-use/when-not versus siblings, and no statement of prerequisites such as the comment needing to exist or permission requirements.

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