Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

generate_bulk_posts

Create and schedule multiple social media posts across a date range in the background. Set platform, frequency, and posting times to automate content delivery.

Instructions

Generate and schedule multiple posts across a date range in the background.

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": {
      "platform": "<platform>",
      "days": "<days>"
    },
    "name": "generate_bulk_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesNumber of days to fill
timesNoComma-separated posting times, e.g. '09:00,14:00'09:00
voiceNoVoice profile ID
brandIdNoBrand ID (uses active brand if omitted)
platformYesPlatform: x | linkedin | instagram | threads | facebook
frequencyNoPosting frequencydaily
postsPerDayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'in the background', which implies asynchronous operation, but does not explain what that entails (e.g., job creation, polling via list_jobs, or cancellation options). Critical behavioral context such as whether this creates drafts or directly publishes is missing.

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 sentence that is concise and front-loaded with the primary purpose. It contains no fluff or redundancy, earning full marks for conciseness.

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 tool's complexity (7 parameters, 2 required) and lack of output schema or annotations, the description is too minimal. It does not explain the background process, how results are returned or tracked, or what 'schedule' entails (e.g., publishing vs. drafting). This is insufficient for an agent to fully understand the operation's behavior and side effects.

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 high (86%), so most parameters are already described. The tool description itself adds no parameter-specific meaning beyond what the schema provides. This is an adequate baseline given the schema's richness.

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

Purpose5/5

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

The description clearly specifies the action ('Generate and schedule') and the resource ('multiple posts across a date range'). This distinguishes it from single-post tools like 'generate_post' or 'schedule_post'. The 'multiple posts' and 'date range' phrasing makes the bulk scope obvious.

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 implies usage for bulk scheduling but does not explicitly state when to choose this over alternatives like 'schedule_post' or 'reschedule_post'. No exclusions or alternative recommendations are given, so the guidance is only implicit.

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

Deploy Server

Other Tools