Skip to main content
Glama

fc_create_space

Create a new community space in FluentCommunity with customizable title, description, privacy settings, and space type for organizing discussions and content.

Instructions

Create a new space in FluentCommunity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesSpace title
slugNoSpace slug (URL-friendly name)
descriptionNoSpace description
typeNoSpace type
privacyNoPrivacy settingpublic
statusNoSpace statusactive

Implementation Reference

  • Handler function that implements fc_create_space: prepares space data (title, slug, privacy, status, description) and sends POST request to WordPress REST API endpoint 'fc-manager/v1/spaces'.
    fc_create_space: async (args: any) => {
      try {
        const spaceData: any = {
          title: args.title,
          slug: args.slug || args.title.toLowerCase().replace(/\s+/g, '-'),
          privacy: args.privacy || 'public',
          status: args.status || 'active',
        };
        
        if (args.description) spaceData.description = args.description;
        
        const response = await makeWordPressRequest('POST', 'fc-manager/v1/spaces', spaceData);
        return { toolResult: { content: [{ type: 'text', text: JSON.stringify(response, null, 2) }] } };
      } catch (error: any) {
        return { toolResult: { isError: true, content: [{ type: 'text', text: `Error: ${error.message}` }] } };
      }
    },
  • Zod input schema defining parameters for fc_create_space tool: title (required), slug, description, privacy, status.
    const createSpaceSchema = z.object({
      title: z.string().describe('Space title'),
      slug: z.string().optional().describe('Space slug (URL-friendly name)'),
      description: z.string().optional().describe('Space description'),
      privacy: z.enum(['public', 'private']).optional().default('public').describe('Privacy setting'),
      status: z.enum(['active', 'inactive']).optional().default('active').describe('Space status')
  • Tool registration in fluentCommunityTools array (Tool[]), specifying name, description, and inputSchema from createSpaceSchema.
    {
      name: 'fc_create_space',
      description: 'Create a new space in FluentCommunity',
      inputSchema: { type: 'object', properties: createSpaceSchema.shape }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Create' which implies a write/mutation operation, but doesn't disclose any behavioral traits: no information about permissions required, whether creation is reversible, rate limits, what happens on duplicate slugs, or what the response contains. This is a significant gap 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 that states the core purpose without any wasted words. It's appropriately sized and front-loaded with the essential information.

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 creation/mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects (permissions, side effects), response format, or usage context. The high schema coverage helps with parameters, but other critical context is missing.

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 6 parameters thoroughly with descriptions, enums, and defaults. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline expectation when schema coverage is high.

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 verb ('Create') and resource ('new space in FluentCommunity'), making the purpose immediately understandable. It distinguishes from siblings like fc_update_space (update) and fc_list_spaces (list), though it doesn't explicitly mention these distinctions in the description text itself.

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. It doesn't mention prerequisites (e.g., permissions needed), when not to use it, or how it differs from similar tools like fc_update_space for modifying existing spaces.

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/wplaunchify/fluent-community-mcp'

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