Skip to main content
Glama

buddypress_create_group

Create new BuddyPress groups with customizable settings including name, description, status, and forum options to build online communities.

Instructions

Create a new group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesGroup name
descriptionNoGroup description
statusNoGroup status (public, private, hidden)
enable_forumNoEnable group forum
creator_idNoCreator user ID (default: current user)

Implementation Reference

  • Executes the buddypress_create_group tool by making a POST request to the BuddyPress REST API /groups endpoint using the provided input arguments.
    else if (name === 'buddypress_create_group') {
      result = await buddypressRequest('/groups', 'POST', args);
    }
  • Defines the tool metadata including name, description, and input schema for validating parameters when creating a BuddyPress group.
    name: 'buddypress_create_group',
    description: 'Create a new group',
    inputSchema: {
      type: 'object',
      properties: {
        name: { type: 'string', description: 'Group name', required: true },
        description: { type: 'string', description: 'Group description' },
        status: { type: 'string', description: 'Group status (public, private, hidden)' },
        enable_forum: { type: 'boolean', description: 'Enable group forum' },
        creator_id: { type: 'number', description: 'Creator user ID (default: current user)' },
      },
      required: ['name'],
    },
  • src/index.ts:528-530 (registration)
    Registers the ListTools handler which returns the array of all tools including buddypress_create_group.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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. It states 'Create a new group' but doesn't explain what happens upon creation (e.g., default settings, permissions required, whether it's reversible via 'buddypress_delete_group', or any side effects like notifications). This leaves significant gaps for a mutation tool.

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 ('Create a new group') that is front-loaded and wastes no words. It directly conveys the core action without unnecessary elaboration, making it highly concise.

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 the complexity of a creation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., permissions, side effects), usage context, and what the tool returns, which are critical for an AI agent to invoke it correctly in a real-world scenario.

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 schema description coverage is 100%, with all parameters well-documented in the schema (e.g., 'status' options: public, private, hidden). The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 for adequate but not enhanced coverage.

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 'Create a new group' clearly states the verb ('Create') and resource ('group'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'buddypress_update_group' or 'buddypress_delete_group' beyond the basic action, which prevents a perfect score.

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. For example, it doesn't mention prerequisites (e.g., user permissions), when to choose this over 'buddypress_update_group', or how it relates to sibling tools like 'buddypress_add_group_member' for group management.

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