Skip to main content
Glama

Create Basecamp Message

basecamp_create_message

Create a new message in a Basecamp message board with subject, HTML content, optional category, and status (active or draft).

Instructions

Create a new message in a Basecamp message board.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
message_board_idYesBasecamp resource identifier
subjectYesMessage subject/title
contentNoHTML message content. 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 <p> for paragraphs. Use <p><br></p> for empty line spacing between paragraphs. * Headings: use <h2>, <h3>, <h4> as appropriate. * Inline code: <code>text</code>. Preformatted blocks: <pre>text</pre>. * Ordered lists: <ol><li>...</li></ol>. Unordered: <ul><li>...</li></ul>. * Tables: <table><tbody><tr><th>Heading</th>...</tr><tr><td>Cell</td>...</tr></tbody></table> * To mention people: <bc-attachment sgid="{ person.attachable_sgid }" content-type="application/vnd.basecamp.mention"></bc-attachment> * Single image: <bc-attachment sgid="{ attachment.attachable_sgid }"></bc-attachment> * Image gallery: wrap multiple <bc-attachment sgid="..." presentation="gallery"> in a <div>. * Basecamp auto-enriches bc-attachment tags after saving (adds url, href, filename, content-type, etc.) — you never need to write those. * To consume less tokens, existing <bc-attachment> tags can be rewritten keeping only: sgid, presentation, caption. For mentions also keep content-type="application/vnd.basecamp.mention". Drop everything else including inner HTML. * Background highlights: <mark style="background-color: var(--highlight-bg-N);">...</mark> * Text color highlights: <span style="color: var(--highlight-N);">...</span> * 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).
message_type_idNoOptional message type/category ID
statusNoMessage status. Use "active" to publish, "drafted" to save as an unpublished draft.active
Behavior3/5

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

Annotations indicate mutation (readOnlyHint=false) and non-destructive nature, but the description adds no further behavioral context such as authentication needs or side effects. The description does not contradict annotations.

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 a single concise sentence front-loaded with the action. It is appropriately brief but could benefit from a bit more detail.

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

Completeness2/5

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

The tool has 5 parameters including complex content with HTML rules, but the description does not mention any of this complexity or the draft status option, leaving important context missing.

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 descriptions for all parameters, so baseline is 3. The description adds no additional parameter meaning beyond the schema.

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 the verb 'Create' and the resource 'message in a Basecamp message board', distinguishing it from sibling tools like basecamp_create_todo or basecamp_create_comment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, no prerequisites, and no context about the message board or when to use draft vs published status.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stefanoverna/basecamp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server