Enterprise Threads MCP Server

bulk_post_management

Perform bulk operations on Threads posts: analyze performance, edit content, audit, export data, and filter by date, type, engagement, or performance threshold.

Instructions

Manage multiple posts with bulk operations and analytics

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "bulk_post_management"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Bulk operation to perform
`filters`	No
`bulk_operations`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv5.1.0Aug 14, 2026

TDQS

D1.5/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'manage' without indicating side effects, permissions, or whether operations are destructive (e.g., archive_low_performers). It fails to disclose any concrete behavioral traits, leaving the agent in the dark about the tool's impact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, so it is not verbose, but it is severely under-specified for a tool with nested objects and multiple actions. It sacrifices necessary detail for brevity, making it inadequate as a functional guide.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, nested structures, no annotations, no output schema), the description is glaringly incomplete. It lacks any explanation of return values, side effects, or behavior, making it insufficient for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds zero parameter semantics. Schema coverage is low (33%), with many fields lacking descriptions, and the description does not compensate by explaining filters, bulk_operations, or the action enum. The agent cannot infer parameter meaning from this description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Manage multiple posts with bulk operations and analytics' is vague and largely restates the tool name. It does not mention the specific actions (analyze_performance, bulk_edit, content_audit, export_data) defined in the schema, nor does it distinguish this tool from siblings like get_content_performance_report or analyze_best_posting_times.

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 does not mention any context, prerequisites, or exclusions, leaving the agent without meaningful direction for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server