Basecamp MCP Server

List Kanban Columns

basecamp_list_kanban_columns

Read-onlyIdempotent

List all columns in a Kanban board given its card table identifier.

Instructions

List all columns in a kanban board.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "card_table_id": "<card_table_id>"
    },
    "name": "basecamp_list_kanban_columns"
  }
}

Input Schema

Name	Required	Description	Default
`card_table_id`	Yes	Basecamp resource identifier

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.2.1Jun 19, 2026

removedInput schema / properties / bucket_id

Removed value: -{
-  "description": "Basecamp resource identifier",
-  "type": "number"
-}

removedInput schema / properties / card_table_id / $ref
```
Removed value: -"#/properties/bucket_id"
```
addedInput schema / properties / card_table_id / description
```
Added value: +"Basecamp resource identifier"
```
addedInput schema / properties / card_table_id / type
```
Added value: +"number"
```

changedInput schema / required

Previous value: -[
-  "bucket_id",
-  "card_table_id"
-]New value: +[
+  "card_table_id"
+]

Addedv1.0.0Jan 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, indicating a safe read operation. The description adds no further behavioral traits (e.g., no side effects, pagination, or rate limits), so it contributes minimal extra transparency.

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 concise sentence with no unnecessary words, perfectly front-loaded with the action and resource.

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?

For a simple list tool with one parameter and rich annotations, the description is adequate but lacks details about the output format (e.g., column names, order). No output schema is provided, so the description could be more helpful.

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% as the single parameter 'card_table_id' has a description 'Basecamp resource identifier'. The tool description does not add any additional context or clarifications beyond the schema, so it meets the baseline.

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 'List all columns in a kanban board' clearly states the action (list) and resource (columns in a kanban board), distinguishing it from siblings like basecamp_list_kanban_cards and basecamp_get_kanban_card.

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 is provided. The description lacks context on prerequisites, such as the need for a card_table_id, and does not mention when to prefer listing columns over listing cards or other operations.

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

Deploy Server