Skip to main content
Glama

fc_bulk_update_posts

Update multiple posts simultaneously to modify status, privacy settings, or post type across your FluentCommunity WordPress site in one operation.

Instructions

Update multiple posts at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idsYesArray of post IDs to update
updatesYesFields to update on all posts

Implementation Reference

  • Handler function for fc_bulk_update_posts tool. Makes a POST request to the WordPress API endpoint 'fc-manager/v1/posts/bulk-update' with post_ids and updates.
    fc_bulk_update_posts: async (args: any) => {
      try {
        const response = await makeWordPressRequest('POST', 'fc-manager/v1/posts/bulk-update', {
          post_ids: args.post_ids,
          updates: args.updates,
        });
        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 schema defining the input parameters for the fc_bulk_update_posts tool: array of post IDs and update fields (status, privacy).
    const bulkUpdatePostsSchema = z.object({
      post_ids: z.array(z.number()).describe('Array of post IDs to update'),
      updates: z.object({
        status: z.string().optional(),
        privacy: z.string().optional()
      }).describe('Fields to update on all posts')
    });
  • Tool registration entry in the fluentCommunityTools array, specifying name, description, and input schema.
    {
      name: 'fc_bulk_update_posts',
      description: 'Update multiple FluentCommunity posts at once',
      inputSchema: { type: 'object', properties: bulkUpdatePostsSchema.shape }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Update multiple posts at once' implies a write/mutation operation but doesn't disclose behavioral traits like whether it's atomic, reversible, requires specific permissions, has rate limits, or what happens on partial failures. For a bulk mutation tool with zero annotation coverage, this is a significant gap in safety and operational context.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place by conveying the bulk nature of the operation.

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 bulk mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as error handling, performance implications, return values, or how updates are applied across posts. The description alone is inadequate for safe and effective use by an AI agent.

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 fully documents the two parameters (post_ids and updates with sub-fields). The description adds no additional meaning beyond implying 'multiple' relates to post_ids. With high schema coverage, the baseline is 3, and the description doesn't compensate with extra context like format examples or constraints.

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 'Update multiple posts at once' clearly states the action (update) and resource (posts) with the scope modifier 'multiple at once'. It distinguishes from sibling tools like fc_update_post (single post) and fc_bulk_delete_posts (different operation). However, it doesn't specify what fields can be updated, which could further differentiate it.

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 when bulk updates are preferred over single updates (fc_update_post), how it compares to fc_bulk_create_posts or fc_bulk_delete_posts, or any prerequisites like permissions or limitations. Usage is implied by the name but not explicitly stated.

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