PostKing MCP Server

storyline_add_line_item

Add a new line item or deliverable to a storyline strategy. Specify channel, content type, title, description, and optional config to define what the content should achieve.

Instructions

Add a new line item (deliverable) to a storyline's strategy. Specify the channel, type, title, description, and a config map (pass {} if no extra config).

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": {
      "storylineId": "<storylineId>",
      "channel": "<channel>",
      "type": "<type>",
      "title": "<title>",
      "description": "<description>",
      "config": "<config>"
    },
    "name": "storyline_add_line_item"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Content type — e.g. 'post', 'article', 'newsletter', 'video'
`title`	Yes	Line-item headline / title
`config`	Yes	Channel/type-specific configuration — pass {} if none
`brandId`	No	Brand ID (defaults to active brand)
`channel`	Yes	Publishing channel — e.g. 'linkedin', 'twitter', 'blog', 'email'
`targetDate`	No	Target publish date (ISO 8601)
`automatable`	No	Whether PostKing can auto-generate this item (defaults to server-side logic)
`description`	Yes	What this piece of content should achieve or cover
`storylineId`	Yes	Storyline ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.7Aug 4, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It doesn't disclose side effects, permissions, return value, or that this mutates the storyline's strategy. The field list and config tip don't cover behavioral impact, similar to the TDQS 2.9 example.

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?

Two sentences, front-loaded with purpose, and every phrase earns its place. The config guidance is practical and concise without redundancy.

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?

With 9 params, a nested config object, no output schema, and no annotations, the description is thin. It doesn't mention preconditions (e.g., storyline must exist), return behavior, or how to obtain storylineId, though it does provide useful context about strategy ownership.

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 baseline is 3. The description repeats some param names (channel, type, title, description, config) and the 'pass {}' tip mirrors the schema's config description, adding little beyond the structured data.

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 ('Add') and resource ('new line item (deliverable) to a storyline's strategy'), clearly distinguishing it from sibling tools like storyline_update_line_item and storyline_delete_line_item. The relationship to strategy is explicit.

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 word 'new' explicitly indicates this tool is for creating line items, not updating or deleting them, providing clear context. However, it doesn't name alternative tools or explicitly state when not to use it, leaving a slight gap.

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

Deploy Server