PostKing MCP Server

storyline_delete

Archive a storyline by soft-deleting it to remove it from active use while keeping it recoverable. Requires confirmation to complete.

Instructions

Archive (soft-delete) a storyline. Pass confirm: true to proceed. Use storyline_restore to reverse this.

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

Input Schema

Name	Required	Description
`brandId`	No	Brand ID (defaults to active brand)
`confirm`	Yes	Must be true to confirm archiving
`storylineId`	Yes	Storyline ID to archive

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.7Aug 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations present, the description carries the full burden. It discloses key behavioral traits: the operation is a soft-delete (reversible) and requires explicit confirmation via 'confirm: true'. However, it does not mention potential side effects or permission requirements, which is a minor gap.

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 with no fluff, front-loading the primary action and then providing critical instructions. Every sentence earns its place.

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

Completeness5/5

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

For a simple deletion tool with full schema coverage and no output schema, the description covers purpose, confirmation requirement, and reversibility. It is complete enough for an agent to select and invoke the tool correctly.

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?

The schema covers 100% of parameters, so the baseline is 3. The description adds the operational context that 'confirm: true' is required to proceed, but the schema already states this constraint. No additional parameter meaning is provided beyond what the schema offers.

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 'Archive (soft-delete) a storyline' with a specific verb and resource. It distinguishes itself from sibling tools by explicitly noting it is a soft-delete and referencing storyline_restore for reversal.

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?

It provides explicit usage instructions: 'Pass confirm: true to proceed' and identifies the alternative tool for reversing the operation ('Use storyline_restore to reverse this'). This gives clear when-to-use and how-to-use guidance.

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

Deploy Server