postnext

Create a blog plan

create_blog_plan

Create a blog content plan (the "Post Planner") for a brand profile. Topics are generated asynchronously, so the plan returns immediately in status "generating" (poll list_blog_plans for progress). Paid feature (Basic+); Business/Teams plans also auto-generate and publish posts to a connected WordPress blog. Pass brandProfileId to choose the brand (defaults to the team's active profile) and integrationId to publish to a specific blog (defaults to the single connected one). NOTE: on Business/Teams with a connected blog, generated posts AUTO-PUBLISH to WordPress by default; pass autoPublish:false to keep them as drafts.

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": {
      "startDate": "<startDate>"
    },
    "name": "create_blog_plan"
  }
}

Input Schema

Name	Required	Description	Default
`planDays`	No
`timezone`	No
`startDate`	Yes
`autoPublish`	No
`integrationId`	No
`brandProfileId`	No
`contentLanguage`	No
`competitorDomains`	No

Output Schema

Name	Required	Description	Default
`planId`	Yes
`status`	Yes
`planDays`	Yes
`startDate`	No
`topicCount`	Yes
`dashboardUrl`	Yes
`integrationId`	Yes
`brandProfileId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedSep 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: asynchronous generation, the returned 'generating' status, the plan-tier requirement (Basic+), and the critical default that Business/Teams auto-publishes to WordPress unless autoPublish:false is passed. That last point is a consequential side effect an agent could not infer from readOnlyHint/destructiveHint alone.

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

Conciseness4/5

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

Front-loaded with the core action and async return behavior, then parameter defaults, then the auto-publish warning. Efficient overall, though the closing NOTE restates publishing behavior already implied earlier, adding a small amount of redundancy.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and the description correctly conveys the immediate 'generating' response plus tier gating and side effects. The remaining gap is the unaddressed date/range/language/competitor parameters, which an agent must infer from bare schema constraints.

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?

With 0% schema description coverage, the description must carry all parameter meaning, and it only covers brandProfileId, integrationId, and autoPublish (including their defaults and behavior). Five parameters — startDate (required), planDays, timezone, contentLanguage, competitorDomains — are left entirely undocumented beyond type and constraints.

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?

States a specific verb and resource ('Create a blog content plan') and names the artifact ('Post Planner') and owning entity (brand profile). It is clearly distinguishable from siblings like create_post_draft and list_blog_plans, which it explicitly references as the polling target.

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

Usage Guidelines4/5

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

Gives concrete operational routing: poll list_blog_plans for progress, pass brandProfileId to pick a brand, integrationId to target a blog. It also flags the paid tier gate. It stops short of saying when to use this versus create_post_draft, so it is clear context without explicit exclusions.

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

All postnext tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?