Basecamp MCP Server

List Basecamp Todos

basecamp_list_todos

Read-onlyIdempotent

Retrieve todos from a Basecamp todo list, filter by active or archived status. Returns todos in display order and includes all groups, even empty ones.

Instructions

List todos in a todo list. Filter by status: 'active' or 'archived'. The todos come in display order: first the todos that are not in a group, then the todos of each group. The response also lists the groups (sections) of the todo list, also the empty groups.

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": {
      "todolist_id": "<todolist_id>"
    },
    "name": "basecamp_list_todos"
  }
}

Input Schema

Name	Required	Description	Default
`status`	No		active
`completed`	No
`todolist_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 / 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"
-]New value: +[
+  "todolist_id"
+]

Changed3 schema fields changedv1.0.3Apr 29, 2026
- addedInput schema / properties / completed / const
```
Added value: +true
```
- removedInput schema / properties / completed / enum
```
Removed value: -[
-  "true"
-]
```
- changedInput schema / properties / completed / type
```
Previous value: -"string"New value: +"boolean"
```
Changed2 schema fields changedv1.0.0Jan 4, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedOct 25, 2025

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral value by disclosing the ordering contract (ungrouped todos first, then each group's todos) and that the response includes group sections including empty ones.

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?

Three tight sentences with the core purpose front-loaded and no filler. The ordering detail is a bit dense but each sentence carries distinct information.

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

Completeness4/5

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

With no output schema, the description usefully explains the return shape (display order plus group sections including empty groups), which is exactly what an agent needs. The one gap is the undocumented 'completed' parameter, leaving the definition slightly short of complete for a 3-parameter tool.

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 coverage is only 33%: only todolist_id is documented ('Basecamp resource identifier'). The description restates the status enum values (already in the schema) but says nothing about the third parameter, 'completed' (a boolean const true), which remains unexplained in both places.

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?

States a specific verb and resource ('List todos in a todo list'), which is clearly distinct from siblings like basecamp_get_todoset, basecamp_create_todo, or basecamp_list_recordings. It does not, however, explicitly name an alternative to route against, so it falls short of a 5.

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 explains how to filter ('active' or 'archived') but never says when to choose this tool over siblings such as basecamp_get_todoset, basecamp_list_recordings, or the group/move tools. No prerequisites or exclusions are given, so an agent gets no routing guidance.

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

Deploy Server