Skip to main content
Glama
stefanoverna

Basecamp MCP Server

by stefanoverna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Basecamp Comment

basecamp_update_comment

Update an existing Basecamp comment by replacing, appending, prepending, or search-replacing its content.

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.

  • 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.
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?

Beyond the annotations' read/destructive flags, the description reveals valuable behavior: Basecamp auto-enriches bc-attachment tags after saving, and before partial operations it collapses existing enriched tags back to their minimal form. This prevents the agent from doing unnecessary cleanup and avoids mismatched find strings. It does not discuss idempotency, but the notable behaviors are covered.

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 first sentence fronts the primary purpose and the token-saving advice. The long HTML section is large, but every part supports the agent in generating correct content for a tool that accepts HTML. It is not overly wordy for the subject matter, although some rules could have been moved to a linked style guide.

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 is strong enough for an agent to operate effectively: it explains how to handle content, how partial operations behave, and how bc-attachment tags are processed. It does not mention return values, but there is no output schema to satisfy. A mention that the updated comment is returned would push it to a 5, but the current coverage is good.

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 meaningful guidance by recommending partial operations to save tokens and explaining how append/prepend/search_replace interact with bc-attachment tags (auto-collapsed first). It also supplies essential HTML formatting rules for constructing valid content values, providing more semantic help than the schema alone.

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 description opens with 'Update a comment', a specific verb and resource, which clearly sets it apart from sibling create_comment and list_comments. It does not explicitly contrast itself with these siblings or state that it operates on existing comments, so it stops short of a 5.

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 instruction to use partial content operations when possible is good parameter-level guidance, but it does not explicitly say when to choose this tool over alternatives such as create_comment or update_message. The intended use is implied by the name and title rather than stated explicitly.

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