Skip to main content
Glama

fc_bulk_create_posts

Create multiple WordPress community posts simultaneously to manage AI-generated content campaigns with scheduled publishing options.

Instructions

Create multiple posts at once (useful for AI-generated content campaigns)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postsYesArray of post objects to create

Implementation Reference

  • The main handler function for the fc_bulk_create_posts tool. It extracts the posts array from input args and performs a bulk POST request to the WordPress REST API endpoint 'fc-manager/v1/posts/bulk', returning the response or error.
    fc_bulk_create_posts: async (args: any) => {
      try {
        const response = await makeWordPressRequest('POST', 'fc-manager/v1/posts/bulk', { posts: args.posts });
        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 for fc_bulk_create_posts defining the structure: an object with 'posts' array, each post having space_id (number), user_id (number), title/message/type/status (strings, optional except message).
    const bulkCreatePostsSchema = z.object({
      posts: z.array(z.object({
        space_id: z.number(),
        user_id: z.number(),
        title: z.string().optional(),
        message: z.string(),
        type: z.string().optional(),
        status: z.string().optional()
      })).describe('Array of post objects to create')
    });
  • Tool registration definition in fluentCommunityTools array, specifying name, description, and inputSchema (referencing the Zod schema). This array is later spread into allTools and registered in the MCP server.
    {
      name: 'fc_bulk_create_posts',
      description: 'Create multiple FluentCommunity posts at once (useful for AI-generated content campaigns)',
      inputSchema: { type: 'object', properties: bulkCreatePostsSchema.shape }
    },
  • Inclusion of fluentCommunityTools (containing fc_bulk_create_posts) into the master allTools array, which is used for MCP server registration.
    ...fluentCommunityTools,       // 21 tools (FluentCommunity spaces, posts, members)
  • Inclusion of fluentCommunityHandlers (containing fc_bulk_create_posts handler) into the master toolHandlers object.
    ...fluentCommunityHandlers,
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 this is a creation tool but doesn't mention permissions needed, rate limits, whether it's transactional (all-or-nothing), error handling for partial failures, or what the response looks like. For a bulk mutation tool, this is a significant gap.

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 perfectly concise - one sentence that directly states the purpose with a helpful parenthetical about use cases. Every word earns its place with zero waste or redundancy.

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 bulk creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens on success/failure, return values, error conditions, or important behavioral aspects like whether posts are created synchronously/asynchronously. The context signals show complexity (nested objects in parameters) that warrants more explanation.

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 the single 'posts' parameter and its nested structure. The description adds no additional parameter information beyond what's in the schema, which is acceptable given the high schema coverage but doesn't provide extra 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 verb ('Create multiple posts') and resource ('posts'), making the purpose immediately understandable. It distinguishes from the sibling 'fc_create_post' by specifying bulk creation, though it doesn't explicitly mention all differences like batch vs single operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some context with 'useful for AI-generated content campaigns', which implies a use case but doesn't give explicit guidance on when to choose this over 'fc_create_post' or other alternatives. No when-not-to-use guidance or prerequisites are mentioned.

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