Skip to main content
Glama
stefanoverna

Basecamp MCP Server

by stefanoverna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Basecamp Todo

basecamp_create_todo

Add a new task to a Basecamp todo list, setting due date, assignees, and notifications as needed.

Instructions

Create a new todo item in a todo list.

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
titleYes
due_onNoDue date in YYYY-MM-DD format. Pass an empty string to leave the due date unset.
notifyNoWhether to notify the assignees about this todo
contentNo
starts_onNoStart date in YYYY-MM-DD format (for a date range; requires due_on). Pass an empty string to leave it unset.
todolist_idYesBasecamp resource identifier
assignee_idsNoArray of person IDs to assign to this todo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.2.1
    • changedInput schema / properties / assignee_ids / items / $ref
      Previous value: -"#/properties/bucket_id"New value: +"#/properties/todolist_id"
    • removedInput schema / properties / bucket_id
      Removed value: -{
-  "description": "Basecamp resource identifier",
-  "type": "number"
-}
    • addedInput schema / properties / due_on
      Added value: +{
+  "description": "Due date in YYYY-MM-DD format. Pass an empty string to leave the due date unset.",
+  "pattern": "^(\\d{4}-\\d{2}-\\d{2})?$",
+  "type": "string"
+}
    • addedInput schema / properties / notify
      Added value: +{
+  "description": "Whether to notify the assignees about this todo",
+  "type": "boolean"
+}
    • addedInput schema / properties / starts_on
      Added value: +{
+  "$ref": "#/properties/due_on",
+  "description": "Start date in YYYY-MM-DD format (for a date range; requires due_on). Pass an empty string to leave it unset."
+}
    • removedInput schema / properties / todolist_id / $ref
      Removed value: -"#/properties/bucket_id"
    • addedInput schema / properties / todolist_id / description
      Added value: +"Basecamp resource identifier"
    • addedInput schema / properties / todolist_id / type
      Added value: +"number"
    • changedInput schema / required
      Previous value: -[
-  "bucket_id",
-  "todolist_id",
-  "title"
-]New value: +[
+  "todolist_id",
+  "title"
+]
  2. Changed7 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / assignee_ids
      Added value: +{
+  "description": "Array of person IDs to assign to this todo",
+  "items": {
+    "$ref": "#/properties/bucket_id"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / content / minLength
      Removed value: -1
    • removedInput schema / properties / description
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / title
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "bucket_id",
-  "todolist_id",
-  "content"
-]New value: +[
+  "bucket_id",
+  "todolist_id",
+  "title"
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The description discloses important processing behaviors, such as Basecamp auto-enriching bc-attachment tags after saving and automatically collapsing already-enriched tags to minimal form before content append/prepend operations. This goes beyond the basic annotations (readOnlyHint=false, idempotentHint=false) and provides useful implementation details.

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 begins with a concise purpose statement, followed by a well-structured list of HTML rules. While long, every bullet point is necessary for correctly formatting content, and the organization aids readability.

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

Completeness3/5

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

The description covers content formatting thoroughly but does not mention return values, error handling, or other side effects beyond creation. Given the absence of an output schema and the straightforward nature of a create operation, this is sufficient, though a brief note on the expected response would improve completeness.

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 descriptions cover 71% of parameters. The description adds significant meaning to the 'content' parameter by detailing allowed HTML elements and formatting rules. It also clarifies due_on and starts_on behavior through schema descriptions, leaving little ambiguity.

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 todo item in a todo list.' It identifies the specific action (create) and resource (todo), distinguishing it from siblings like basecamp_update_todo and basecamp_list_todos.

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 description provides extensive HTML formatting rules for the content parameter, which serves as usage guidance for how to format content. However, it does not explicitly mention when to use this tool versus alternatives (e.g., update_todo), leaving the selection criterion implied by the name and purpose.

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