BuddyPress MCP Server

buddypress_get_xprofile_data

Retrieve extended profile data for specific users and fields in BuddyPress community sites. Use this tool to access user profile information programmatically through the REST API.

Instructions

Get XProfile data for a specific user and field

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": {
      "field_id": "<field_id>",
      "user_id": "<user_id>"
    },
    "name": "buddypress_get_xprofile_data"
  }
}

Input Schema

Name	Required	Description	Default
`field_id`	Yes	Field ID
`user_id`	Yes	User ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 11, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits such as read-only nature, authentication needs, error handling, rate limits, or what the returned data looks like, which are critical for a tool with no output schema.

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 with zero waste. It front-loads the core purpose clearly and appropriately sized for a simple retrieval tool.

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 a simple input schema, the description is incomplete. It lacks details on return values, error cases, or behavioral context, making it inadequate for the agent to fully understand how to use this tool effectively.

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 both parameters ('field_id' and 'user_id'). The description adds no additional meaning beyond implying these are required for targeting, matching the baseline for high schema coverage without extra param details.

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 ('Get') and resource ('XProfile data') with specific targeting ('for a specific user and field'). It distinguishes from siblings like 'buddypress_get_xprofile_field' or 'buddypress_update_xprofile_data' by focusing on data retrieval rather than field metadata or updates, though it doesn't explicitly contrast them.

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, context, or compare to siblings like 'buddypress_get_member' or 'buddypress_list_xprofile_fields', leaving the agent to infer usage from the name alone.

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

Deploy Server