Skip to main content
Glama

List Basecamp Activity (Recordings)

basecamp_list_recordings
Read-onlyIdempotent

Browse recent activity across Basecamp projects by listing all content types (todos, messages, documents, comments, uploads). Filter by project, person, time, type, title text, and more to find specific updates.

Instructions

Browse recent activity across Basecamp by listing recordings. Recordings represent all content in Basecamp: todos, messages, documents, comments, uploads, and more.

Use this tool to:

  • See what's been happening across all projects or specific projects

  • Find recent activity by one or more people

  • Review changes since a specific date or time period

  • Filter activity by content type (todos, messages, documents, etc.)

  • Search activity by title text

When to use this vs. the per-resource list tools: use the per-project list tools (basecamp_list_messages, basecamp_list_todos, basecamp_list_documents, basecamp_list_comments, basecamp_list_kanban_cards) to browse items WITHIN a single project; use basecamp_list_recordings for CROSS-project, time-based, or multi-type activity browsing.

All filters support multiple values for OR-matching.

Examples:

  • "What happened in the last 24 hours?" → since: "24h"

  • "Show recent todos in project 12345" → project_ids: [12345], type: ["todo"]

  • "What did Alice and Bob do this week?" → person_ids: [111, 222], since: "7d"

  • "Find messages mentioning launch across projects 1 and 2" → project_ids: [1, 2], type: ["message"], query: ["launch"]

  • "Find items about design or UX" → query: ["design", "UX"]

  • "List all messages across projects" → type: ["message"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idsNoFilter to specific projects (bucket IDs). Supports multiple IDs for OR-matching. Omit to browse across all projects.
typeNoRecording type filter. Options: "todo", "message", "document", "comment", "upload", "todolist", "question", "schedule", "vault". Supports multiple values for OR-matching. Omit to fetch all common types (todo, message, document, comment, upload, card).
sinceNoShow activity since this time. Accepts ISO 8601 dates (e.g., "2024-01-15"), relative durations ("24h", "7d", "2w"), or keywords ("today", "yesterday").
person_idsNoFilter by creator person IDs. Supports multiple IDs for OR-matching. Use basecamp_list_people to find person IDs.
queryNoCase-insensitive text search against recording titles. Supports multiple terms for OR-matching.
sortNoSort field: "created_at" (default) or "updated_at".
directionNoSort direction: "desc" (default, newest first) or "asc" (oldest first).
statusNoRecording status filter: "active" (default), "archived", or "trashed".
limitNoMaximum number of recordings to return (default: 20, max: 100).
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that filters support multiple values for OR-matching, default behavior when omitting parameters, and lists specific recording types. No contradictions.

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 well-structured with a clear introduction, bullet points for use cases, an explicit comparison to sibling tools, and specific examples. Every sentence contributes value without redundancy.

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

Completeness5/5

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

With 9 parameters, all fully described in both schema and description, and no output schema (recordings list is self-explanatory), the description is complete with examples covering various scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant context: clarifies that project_ids can be omitted to browse all projects, type defaults to common types, since accepts ISO/relative/keywords, query is case-insensitive, limit default and max, and provides multiple examples.

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 clearly states the tool browses recent activity across Basecamp by listing recordings, explaining that recordings represent all content types. It distinguishes itself from per-resource list tools by noting cross-project, time-based, or multi-type activity browsing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly includes a 'When to use this vs. the per-resource list tools' section, naming specific alternatives like basecamp_list_messages, basecamp_list_todos, etc., and states when to use each.

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

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/stefanoverna/basecamp-mcp'

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