PostKing MCP Server

storyline_create

Create a new marketing storyline for a brand from a campaign goal prompt, optionally with a custom title. Kickstart the planning process for subsequent clarification and brief generation.

Instructions

Create a new storyline (marketing plan) for the brand. Pass a prompt describing the campaign goal; optionally provide a title. After creation, call storyline_clarify to gather context, then storyline_generate_brief.

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": {
      "prompt": "<prompt>"
    },
    "name": "storyline_create"
  }
}

Input Schema

Name	Required	Description
`title`	No	Optional display title (auto-generated if omitted)
`prompt`	Yes	Campaign goal or intent — e.g. 'Q3 product launch for Feature X targeting SMBs'
`brandId`	No	Brand ID (defaults to active brand)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.7Aug 4, 2026

TDQS

A4/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 burden. It discloses that the tool creates a new storyline and hints at a workflow, but it does not mention side effects, permissions, idempotency, or what the response contains. This is a moderate level of transparency for a create tool.

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 two sentences: the first states the action and resource, the second provides the workflow. It is front-loaded, precise, and contains no redundant information.

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 simple create tool with 3 params and no output schema, the description is mostly complete. It explains how to invoke it and what to do next. However, it does not explicitly state what is returned (e.g., storyline ID), which is necessary for subsequent calls like storyline_clarify. This minor gap prevents a perfect score.

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 100%, so the baseline is 3. The description rephrases the prompt purpose ('describe the campaign goal') and mentions the optional title, but adds no new meaning beyond the schema. BrandId is not mentioned in the description, but the schema covers it adequately.

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 uses a specific verb ('Create') with a clear resource ('a new storyline (marketing plan) for the brand'). It distinguishes from sibling tools like storyline_update and storyline_restore by explicitly noting 'new' and by describing the creation workflow. The next-step instructions further clarify its role as the entry point.

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 says to follow with storyline_clarify then storyline_generate_brief, providing clear when-to-use context. However, it does not mention when not to use it or name alternatives (e.g., storyline_update) explicitly, so it falls short of a 5.

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

Deploy Server