BlackOps Center

Create Post

post_posts

Create a blog draft. Before calling, fetch get_me + get_brand_voice (+ get_ai_context/get_recent_notes). Site scope is automatic for a single-site account; pass domain or site_id to target one, and an account with several sites is asked to choose rather than guessed at. Do NOT repeat the title in the content body — no leading "# Title" and no first line restating it, or it renders twice, since the title field prints above the content. Start with the intro paragraph or the first ## heading. The response carries links.review_url: that is where a person previews and edits the draft, so hand the user that link, never the admin editor URL or a raw preview URL.

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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "post_posts"
  }
}

Input Schema

Name	Required	Description
`slug`	No
`tags`	No
`title`	Yes
`domain`	No
`source`	No
`status`	No
`confirm`	No
`content`	Yes	Blog post body in Markdown. Do NOT pass a fully HTML-formatted document — block-level HTML tags (e.g. <p>, <h2>) appear as literal text. Custom styled HTML (cards, tables, CSS callouts) must go in a richembed fenced block, which renders live. Inline HTML for embeds or Remotion components inside an otherwise-Markdown post is fine.
`excerpt`	No
`site_id`	No
`featured`	No
`subtitle`	No	Subtitle/deck shown beneath the title. Populate it whenever the post has a natural subheadline or clarifying phrase.
`seo_title`	No
`seo_description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare destructiveHint=false, so the description carries the burden and does so well: it discloses the multi-site ambiguity behavior (asks rather than guesses), a rendering side effect (title field prints above content, so repeating it duplicates the heading), and the return contract (links.review_url is the human-facing preview link). It even specifies which URL to hand the user and which to avoid, which no structured field provides.

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 action, then preconditions, then pitfalls, then output handling — a sensible order with no filler sentences. It is dense and runs long, but each sentence carries distinct operational information rather than restating the schema.

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?

For a 14-parameter creation tool with no output schema, the description covers the highest-risk gaps: prerequisite context fetches, site targeting, the title/content duplication trap, and how to surface the returned review link. The remaining gap is the semantics of status and confirm (whether publishing requires explicit confirmation), which an agent would have to infer.

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 only 14% across 14 parameters, so the description must compensate and it only partly does. It clarifies the two genuinely ambiguous ones — domain/site_id scoping semantics and the title-vs-content relationship — but says nothing about slug, tags, source, status, confirm, excerpt, featured, seo_title, or seo_description, including the potentially consequential confirm flag.

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?

States a specific verb and resource ("Create a blog draft") and the sibling set makes clear it is the creation entry point distinct from post_posts_by_id_publish and patch_posts_by_id. Minor narrowing: the schema's status enum also allows "published," so the draft-only framing understates scope, but the core action is unambiguous.

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

Usage Guidelines5/5

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

Explicitly lists prerequisites before calling (get_me, get_brand_voice, optionally get_ai_context/get_recent_notes) and names the exact siblings to fetch first. It also states the when-not for scoping parameters: single-site accounts are auto-scoped, so domain/site_id are only needed to target a specific site, and multi-site accounts are prompted rather than guessed at.

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

All BlackOps Center 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?