Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty

move_column

Reposition a column within a Basecamp card table by specifying its project ID, card table ID, column ID, and new 1-based position.

Instructions

Move a column to a new position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_table_idYesThe card table ID
column_idYesThe column ID
positionYesThe new 1-based position
project_idYesThe project ID

Implementation Reference

  • Core handler logic for moving a column by making the Basecamp API POST request to the moves endpoint.
    async moveColumn(projectId: string, columnId: string, position: number, cardTableId: string): Promise<void> {
      await this.client.post(`/buckets/${projectId}/card_tables/${cardTableId}/moves.json`, {
        source_id: columnId,
        target_id: cardTableId,
        position,
      });
    }
  • src/index.ts:256-269 (registration)
    MCP tool registration for 'move_column', including name, description, and input schema definition. Note: No explicit case handler in the request handler switch statement.
    {
      name: 'move_column',
      description: 'Move a column to a new position',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'The project ID' },
          card_table_id: { type: 'string', description: 'The card table ID' },
          column_id: { type: 'string', description: 'The column ID' },
          position: { type: 'number', description: 'The new 1-based position' },
        },
        required: ['project_id', 'card_table_id', 'column_id', 'position'],
      },
    },
  • Input schema validation for the move_column tool parameters.
    inputSchema: {
      type: 'object',
      properties: {
        project_id: { type: 'string', description: 'The project ID' },
        card_table_id: { type: 'string', description: 'The card table ID' },
        column_id: { type: 'string', description: 'The column ID' },
        position: { type: 'number', description: 'The new 1-based position' },
      },
      required: ['project_id', 'card_table_id', 'column_id', 'position'],
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('move') but doesn't cover critical aspects like whether this is a destructive operation (likely yes, as it modifies column order), permission requirements, error conditions (e.g., invalid position), or what happens to other columns. This leaves significant gaps 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 that front-loads the core action ('move a column') and specifies the outcome ('to a new position'). There is no wasted verbiage or redundancy, making it easy to parse quickly.

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 no annotations and no output schema, the description is insufficient. It lacks details on behavior (e.g., how positions shift, error handling), return values, or integration with sibling tools (e.g., 'get_columns' to check current order). The high schema coverage helps with parameters but doesn't compensate for missing operational context.

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%, with all parameters clearly documented in the schema (e.g., 'card_table_id', 'position' as '1-based'). The description adds no additional parameter semantics beyond implying 'position' is the target location. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('move') and resource ('column'), specifying the target ('to a new position'). It distinguishes from siblings like 'create_column' or 'update_column' by focusing on repositioning, though it doesn't explicitly contrast with 'move_card' which is a similar operation on a different resource.

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. It doesn't mention prerequisites (e.g., needing a column to exist), exclusions, or comparisons to similar tools like 'update_column' or 'move_card', leaving the agent to infer usage context from the tool name alone.

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