Skip to main content
Glama

fc_create_post

Create new posts in FluentCommunity forums by specifying space, user, title, content, and privacy settings to publish or save as draft.

Instructions

Create a new post in FluentCommunity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_idYesThe space ID where the post will be created
user_idYesThe user ID who creates the post
titleNoPost title
messageYesPost content/message
message_renderedNoRendered HTML version of the message
typeNoPost type (text, video, etc.)text
statusNoPost statuspublished
privacyNoPost privacy settingpublic
featured_imageNoURL of the featured image
metaNoAdditional metadata as JSON object

Implementation Reference

  • The async handler function fc_create_post that executes the tool logic by constructing post data and making a POST request to the WordPress FluentCommunity endpoint.
    fc_create_post: async (args: any) => {
      try {
        const postData: any = {
          space_id: args.space_id,
          user_id: args.user_id,
          message: args.message,
          type: args.type || 'text',
          status: args.status || 'published',
          privacy: args.privacy || 'public',
        };
        
        if (args.title) postData.title = args.title;
        
        const response = await makeWordPressRequest('POST', 'fc-manager/v1/posts', postData);
        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 creating a post: space_id, user_id, title, message, type, status, privacy.
    const createPostSchema = z.object({
      space_id: z.number().describe('The space ID where the post will be created'),
      user_id: z.number().describe('The user ID who creates the post'),
      title: z.string().optional().describe('Post title'),
      message: z.string().describe('Post content/message'),
      type: z.string().optional().default('text').describe('Post type (text, video, etc.)'),
      status: z.enum(['published', 'draft', 'pending']).optional().default('published').describe('Post status'),
      privacy: z.enum(['public', 'private', 'friends']).optional().default('public').describe('Post privacy setting')
    });
  • Registration of the fc_create_post tool in the fluentCommunityTools array, linking name, description, and schema.
    {
      name: 'fc_create_post',
      description: 'Create a new post in FluentCommunity',
      inputSchema: { type: 'object', properties: createPostSchema.shape }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't address permissions needed, whether the operation is idempotent, rate limits, error conditions, or what happens on success (e.g., returns a post ID). This leaves significant gaps for an agent to understand the tool's behavior.

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 purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 10 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns a post object or ID), doesn't mention authentication requirements, and provides no context about the FluentCommunity platform. Given the complexity and lack of structured data, more completeness is needed.

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%, meaning all parameters are documented in the input schema. The description adds no additional parameter information beyond what's already in the schema (like explaining relationships between parameters or providing examples). With complete schema coverage, the baseline score of 3 is appropriate.

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 ('Create a new post') and target resource ('in FluentCommunity'), which provides a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like fc_bulk_create_posts or fc_update_post, which would require explicit comparison to achieve a score of 5.

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. With sibling tools like fc_bulk_create_posts (for multiple posts) and fc_update_post (for modifications), there's no indication of when this single-post creation tool is preferred, nor any mention of prerequisites or constraints.

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