Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty

create_column

Add a new column to a card table in Basecamp by specifying the project ID, card table ID, and column title. Simplify project organization and task management directly through API integration.

Instructions

Create a new column in a card table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_table_idYesThe card table ID
project_idYesThe project ID
titleYesThe column title

Implementation Reference

  • MCP tool handler for 'create_column' that calls BasecampClient.createColumn and formats the response.
    case 'create_column': {
      const column = await client.createColumn(typedArgs.project_id, typedArgs.card_table_id, typedArgs.title);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({
            status: 'success',
            column,
            message: `Column '${typedArgs.title}' created successfully`
          }, null, 2)
        }]
      };
    }
  • src/index.ts:231-242 (registration)
    Registration of the 'create_column' tool including its input schema.
      name: 'create_column',
      description: 'Create a new column in a card table',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'The project ID' },
          card_table_id: { type: 'string', description: 'The card table ID' },
          title: { type: 'string', description: 'The column title' },
        },
        required: ['project_id', 'card_table_id', 'title'],
      },
    },
  • Implementation of createColumn method in BasecampClient that makes the API call to create a column.
    async createColumn(projectId: string, cardTableId: string, title: string): Promise<Column> {
      const response = await this.client.post(`/buckets/${projectId}/card_tables/${cardTableId}/columns.json`, {
        title,
      });
      return response.data;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't specify permission requirements, whether this operation is idempotent, what happens on duplicate column titles, or what the response looks like. For a creation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that states the core functionality without unnecessary words. It's front-loaded with the essential action and resource, making it immediately scannable. Every word earns its place, with no redundant information or fluff.

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 creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns the new column object, success status), permission requirements, or error conditions. With 3 required parameters and mutation behavior, more context is needed to help the agent use this tool 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?

The description mentions creating a column 'in a card table,' which implies the need for card_table_id, but doesn't explicitly connect to the three parameters. With 100% schema description coverage, all parameters are documented in the schema itself (card_table_id, project_id, title). The description adds minimal value beyond what the schema provides, meeting the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Create') and resource ('new column in a card table'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'update_column' or 'move_column', but the verb 'Create' distinguishes it from update operations. The description is specific enough to understand what the tool does without being tautological.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'update_column', 'move_column', and 'get_columns', there's no indication of when creation is appropriate versus modification or retrieval. No prerequisites, constraints, or alternative tools are mentioned, leaving the agent to infer usage context.

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