Skip to main content
Glama
stefanoverna

Basecamp MCP Server

by stefanoverna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Basecamp Document

basecamp_update_document

Updates a document in Basecamp by replacing, appending, prepending, or search-replacing its content. Specify the document ID and apply targeted changes to save tokens.

Instructions

Update a document. 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 document title
contentNoIf provided, replaces entire HTML content. Cannot be used with content_append, content_prepend, or search_replace.
document_idYesDocument ID to update
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. Changed2 schema fields changedv1.2.1
    • removedInput schema / properties / bucket_id
      Removed value: -{
-  "description": "Project/bucket ID",
-  "type": "number"
-}
    • changedInput schema / required
      Previous value: -[
-  "bucket_id",
-  "document_id"
-]New value: +[
+  "document_id"
+]
  2. Addedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false and openWorldHint=true, so the tool is a mutation. The description adds valuable behavioral details: bc-attachment tags are auto-enriched after saving and collapsed before content operations, with a warning not to strip them manually. This goes beyond what annotations provide and helps avoid misuse.

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 due to necessary HTML rules, but it is well-structured with bullet points and front-loads the purpose. Every sentence contributes to correct usage, though it could be trimmed slightly without loss of clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of HTML content, mentions, attachments, and multiple update modes, the description is comprehensive. It covers allowed tags, paragraph spacing, headings, lists, tables, mentions, images, highlights, and the behavior of enrichment. There is no output schema, so no return-value documentation is needed. The tool is fully specified for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with all parameters described. The description adds HTML formatting rules relevant to the content parameter, and clarifies the mutual exclusivity of content vs. partial operations (already in schema). This adds some value but doesn't significantly go beyond the schema's own descriptions.

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 opens with a clear 'Update a document.' which is a specific verb and resource. It distinguishes from siblings like basecamp_create_document and basecamp_get_document by its mutation focus on an existing document.

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 explicitly advises 'Use partial content operations when possible to save on token usage', giving clear guidance on parameter selection. It doesn't explicitly name alternatives like create_document, but the purpose is obvious from the context. The guidance is 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