Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

update_document

Modify Basecamp 3 documents by updating titles and HTML content using project and document IDs for precise file management within the Basecamp MCP Server.

Instructions

Update a document

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentNoNew HTML content
document_idYesDocument ID
project_idYesProject ID
titleNoNew title

Implementation Reference

  • src/lib/basecamp-client.ts:352-364 (handler)
    The core handler function that executes the tool logic by making a PUT request to update the document title and/or content in Basecamp.
    async updateDocument(
  projectId: string,
  documentId: string,
  title?: string,
  content?: string
): Promise<Document> {
  const data: any = {};
  if (title) data.title = title;
  if (content) data.content = content;

  const response = await this.client.put(`/buckets/${projectId}/documents/${documentId}.json`, data);
  return response.data;
}
  • src/index.ts:433-446 (schema)
    The input schema and description for the 'update_document' tool, registered in the MCP server's tools list.
    {
  name: 'update_document',
  description: 'Update a document',
  inputSchema: {
    type: 'object',
    properties: {
      project_id: { type: 'string', description: 'Project ID' },
      document_id: { type: 'string', description: 'Document ID' },
      title: { type: 'string', description: 'New title' },
      content: { type: 'string', description: 'New HTML content' },
    },
    required: ['project_id', 'document_id'],
  },
},

Tool Definition Quality

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states 'Update a document' without disclosing behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields. It lacks critical context for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste—'Update a document' is front-loaded and appropriately sized for the tool's purpose, though it could benefit from more detail given the lack of annotations.

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?

For a mutation tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances, leaving significant gaps for an AI agent to operate effectively.

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 description coverage is 100%, so parameters are documented in the schema. The description adds no meaning beyond what the schema provides (e.g., doesn't explain parameter interactions or defaults), meeting the baseline for high coverage without extra value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update a document' states the verb and resource but is vague about what aspects can be updated. It distinguishes from siblings like 'create_document' and 'trash_document' by specifying update rather than create or delete, but doesn't clarify scope beyond the basic action.

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 is provided on when to use this tool versus alternatives like 'update_card' or 'update_column', nor prerequisites such as needing existing document/project IDs. The description implies usage for document updates but offers no context on exclusions or specific scenarios.

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

Related 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/jhliberty/basecamp-mcp-server'

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