BuddyPress MCP Server

buddypress_list_messages

Retrieve and organize user message threads from BuddyPress community sites, filtering by inbox/sentbox, read/unread status, and pagination for efficient management.

Instructions

List message threads

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buddypress_list_messages"
  }
}

Input Schema

Name	Required	Description
`user_id`	No	User ID to get messages for
`box`	No	Message box (inbox, sentbox, notices)
`type`	No	Message type (all, read, unread)
`page`	No	Page number (default: 1)
`per_page`	No	Items per page (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 11, 2025

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'List message threads', implying a read-only operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, pagination behavior (beyond parameters), or what the output format looks like. This leaves significant gaps for an agent to understand how the tool behaves.

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 extremely concise with 'List message threads', a single phrase that front-loads the core purpose without waste. Every word earns its place, making it efficient and easy to parse.

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?

Given no annotations, no output schema, and 5 parameters, the description is incomplete. It doesn't cover behavioral aspects like safety, response format, or error handling. For a listing tool with multiple filtering options, more context is needed to guide effective use, leaving the agent with insufficient information.

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%, so the schema already documents all 5 parameters thoroughly. The description adds no additional meaning beyond the schema, such as explaining relationships between parameters (e.g., how 'box' and 'type' interact) or usage examples. Baseline 3 is appropriate as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'List message threads' clearly states the verb ('List') and resource ('message threads'), providing a basic purpose. However, it doesn't differentiate from siblings like 'buddypress_get_message' (which likely retrieves a single message) or specify what 'threads' means versus individual messages, making it somewhat vague.

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. For example, it doesn't clarify if this is for browsing conversations versus retrieving specific messages (as with 'buddypress_get_message') or how it relates to other listing tools like 'buddypress_list_activities'. The description lacks context for selection.

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

Deploy Server