Skip to main content
Glama

buddypress_update_group

Modify an existing BuddyPress group by updating its name, description, or privacy status using the group ID.

Instructions

Update an existing group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGroup ID
nameNoGroup name
descriptionNoGroup description
statusNoGroup status (public, private, hidden)

Implementation Reference

  • Handler logic that extracts the group ID and body from arguments and makes a PUT request to the BuddyPress /groups/{id} endpoint using the shared buddypressRequest helper.
    else if (name === 'buddypress_update_group') {
      const { id, ...body } = args as any;
      result = await buddypressRequest(`/groups/${id}`, 'PUT', body);
    }
  • src/index.ts:225-238 (registration)
    Registers the buddypress_update_group tool in the tools list, including its name, description, and input schema definition.
    {
      name: 'buddypress_update_group',
      description: 'Update an existing group',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'number', description: 'Group ID', required: true },
          name: { type: 'string', description: 'Group name' },
          description: { type: 'string', description: 'Group description' },
          status: { type: 'string', description: 'Group status (public, private, hidden)' },
        },
        required: ['id'],
      },
    },
  • Input schema defining the parameters for the buddypress_update_group tool: required group ID and optional name, description, status.
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'number', description: 'Group ID', required: true },
        name: { type: 'string', description: 'Group name' },
        description: { type: 'string', description: 'Group description' },
        status: { type: 'string', description: 'Group status (public, private, hidden)' },
      },
      required: ['id'],
    },
  • Helper function that performs authenticated HTTP requests to the BuddyPress REST API endpoints, used by all tool handlers including buddypress_update_group.
    async function buddypressRequest(
      endpoint: string,
      method: string = 'GET',
      body?: any
    ): Promise<any> {
      const url = `${BUDDYPRESS_URL}/wp-json/buddypress/v2${endpoint}`;
      const auth = Buffer.from(`${BUDDYPRESS_USERNAME}:${BUDDYPRESS_PASSWORD}`).toString('base64');
    
      const options: any = {
        method,
        headers: {
          'Authorization': `Basic ${auth}`,
          'Content-Type': 'application/json',
        },
      };
    
      if (body && method !== 'GET') {
        options.body = JSON.stringify(body);
      }
    
      const response = await fetch(url, options);
    
      if (!response.ok) {
        const errorText = await response.text();
        throw new Error(`BuddyPress API Error (${response.status}): ${errorText}`);
      }
    
      return await response.json();
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Update an existing group' implies a mutation operation, but it doesn't disclose permission requirements, whether changes are reversible, rate limits, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, with zero wasted content.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the update operation returns, error conditions, or side effects. Given the complexity of updating a group and the lack of structured behavioral data, more context is needed for the agent 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?

The input schema has 100% description coverage, with clear parameter documentation (e.g., 'Group ID', 'Group status (public, private, hidden)'). The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline for high schema coverage without compensating value.

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 ('Update') and resource ('an existing group'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'buddypress_update_activity' or 'buddypress_update_member', which follow the same 'update [resource]' pattern, so it doesn't fully distinguish from alternatives.

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 provides no guidance on when to use this tool versus alternatives like 'buddypress_create_group' or 'buddypress_delete_group'. It doesn't mention prerequisites (e.g., needing an existing group ID) or contextual constraints, leaving the agent to infer usage from the tool name alone.

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/vapvarun/buddypress-mcp'

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