Skip to main content
Glama
stefanoverna

Basecamp MCP Server

by stefanoverna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Basecamp Document

basecamp_create_document

Create a new document in a specified Basecamp vault with a title, content, and optional status (active or draft).

Instructions

Create a new document in a vault.

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
titleYesDocument title
statusNoDocument status. Use "active" to publish, "drafted" to save as an unpublished draft.active
contentYesHTML document content
vault_idYesVault ID to create the document in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.1
    • removedInput schema / properties / bucket_id
      Removed value: -{
-  "description": "Project/bucket ID",
-  "type": "number"
-}
    • changedInput schema / properties / status / description
      Previous value: -"Document status"New value: +"Document status. Use \"active\" to publish, \"drafted\" to save as an unpublished draft."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "active",
-  "draft"
-]New value: +[
+  "active",
+  "drafted"
+]
    • changedInput schema / required
      Previous value: -[
-  "bucket_id",
-  "vault_id",
-  "title",
-  "content"
-]New value: +[
+  "vault_id",
+  "title",
+  "content"
+]
  2. Addedv1.0.3

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond the annotations to explain important behaviors: the expected HTML subset, how mentions/images/galleries work via bc-attachment tags, that Basecamp auto-enriches attachments after saving, and that existing enriched tags are automatically collapsed before content operations — telling the agent not to strip them manually. This is substantial behavioral disclosure that prevents likely mistakes.

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 well-structured with a clear one-line purpose followed by a bulleted HTML reference. It's lengthy but appropriately so given the complexity of Basecamp's HTML content requirements. Every bullet serves a functional purpose — no filler. The opening sentence is front-loaded.

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?

Given the rich schema (100% parameter coverage) and detailed behavioral notes, the description is quite complete for a create operation. No output schema exists, so the return format isn't specified, but that's a platform limitation rather than a description gap. Minor: could mention that the created document can later be retrieved via get_document or listed via list_documents, but this is not essential.

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 schema already covers 100% of parameters with descriptions. The description adds meaningful value by explaining the content parameter's HTML requirements in depth and clarifying the status enum values. Slight deduction because the description doesn't address vault_id discovery (e.g., how to find vault IDs via list_vaults), though the schema description is adequate.

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 'Create a new document in a vault' — a specific verb (create), resource (document), and location (vault). It is easily distinguished from siblings like basecamp_update_document, basecamp_create_message, or basecamp_create_vault.

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 and schema explain how to use the tool, including a detailed HTML formatting guide and status values ('active' to publish, 'drafted' for drafts). It doesn't explicitly name alternative tools for when NOT to use it, but the clear scope makes usage conditions fairly evident. Minor gap: no mention of when to prefer create_vault or update_document instead.

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