PostKing MCP Server

create_publication

Create a new blog publication that serves as a container for articles. Returns a publicationId required for generating blog posts.

Instructions

Create a new blog publication (the container that articles live under). Returns a publicationId needed for generate_blog_post.

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>"
    },
    "name": "create_publication"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Publication name, e.g. 'My Blog'
`layout`	No
`brandId`	No	Brand ID (uses active brand if omitted)
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.7Aug 4, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full transparency burden. It discloses that the tool creates a publication and returns a publicationId, but does not cover potential side effects, permissions, or error behavior. Some behavioral context is added, but it remains incomplete.

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 efficiently conveys the core purpose, the parenthetical clarifies the resource, and the return value is noted upfront. No wasteful wording.

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

Completeness3/5

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

The description covers the main purpose and return value, and the dependency on generate_blog_post adds context. However, it omits explanations for the layout and description parameters, and does not mention potential prerequisites or failure cases. Given no output schema and no annotations, more detail would be expected.

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

Parameters2/5

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

The tool description does not add meaning to the input parameters beyond the schema. Schema coverage is only 50% (title and brandId have descriptions, layout and description do not), and the description fails to explain the undocumented parameters, leaving gaps for the agent.

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 states the action ('Create a new blog publication') and clarifies the resource as the container for articles. It distinguishes the tool from siblings like generate_blog_post by noting the returned publicationId is required for that tool.

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?

The description explicitly connects this tool to generate_blog_post by stating the publicationId is needed for that tool, giving a clear when-to-use context. It does not mention alternatives like update_publication, but the use case is well-implied.

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

Deploy Server