Skip to main content
Glama

fc_bulk_delete_posts

Remove multiple posts simultaneously from your FluentCommunity platform by specifying post IDs to manage content efficiently.

Instructions

Delete multiple posts at once

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idsYesArray of post IDs to delete

Implementation Reference

  • The core handler function for the fc_bulk_delete_posts tool. It sends a POST request to the WordPress REST API endpoint '/fc-manager/v1/posts/bulk-delete' with the array of post_ids from the input args, and returns the response or an error message.
    fc_bulk_delete_posts: async (args: any) => {
      try {
        const response = await makeWordPressRequest('POST', 'fc-manager/v1/posts/bulk-delete', { post_ids: args.post_ids });
        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 validation for the tool: an object containing 'post_ids' as an array of numbers.
    const bulkDeletePostsSchema = z.object({
      post_ids: z.array(z.number()).describe('Array of post IDs to delete')
    });
  • Tool registration entry in the fluentCommunityTools array, specifying the tool's name, description, and input schema.
    {
      name: 'fc_bulk_delete_posts',
      description: 'Delete multiple FluentCommunity posts at once',
      inputSchema: { type: 'object', properties: bulkDeletePostsSchema.shape }
    },
  • Top-level aggregation of all tools in src/tools/index.ts, spreading fluentCommunityTools which includes fc_bulk_delete_posts.
    ...fluentCommunityTools,       // 21 tools (FluentCommunity spaces, posts, members)
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 the destructive action ('Delete') but lacks crucial details: whether deletions are permanent/reversible, permission requirements, rate limits, error handling for invalid IDs, or confirmation prompts. This is inadequate for a destructive bulk operation.

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 function without unnecessary words. It's appropriately sized and front-loaded with the core action, making it easy 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 destructive bulk operation with no annotations and no output schema, the description is incomplete. It doesn't address critical context like irreversible consequences, authorization needs, response format, or error conditions. Given the high-risk nature of bulk deletion, more comprehensive guidance is warranted.

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%, with the single parameter 'post_ids' well-documented in the schema as an array of numbers. The description adds no additional parameter semantics beyond implying bulk deletion requires multiple IDs, which is already clear from the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Delete multiple posts at once') and identifies the resource ('posts'), making the purpose immediately understandable. It distinguishes from the sibling 'fc_delete_post' by specifying bulk operation, though it doesn't explicitly mention this distinction in the text.

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 like 'fc_delete_post' for single deletions or 'fc_bulk_update_posts' for modifications. There are no prerequisites, exclusions, or context about appropriate scenarios 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