Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

storyline_update

Update a storyline's title, live status, or start/end/launch dates. Provide at least one field to apply changes.

Instructions

Update metadata on a storyline: title, live status, or start/end/launch dates. Pass at least one field to change.

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

Input Schema

NameRequiredDescriptionDefault
titleNoNew display title
isLiveNoWhether the storyline is currently live/active
brandIdNoBrand ID (defaults to active brand)
launchDateNoISO 8601 launch date, or null to clear it
storylineIdYesStoryline ID
storylineEndDateNoISO 8601 end date for the storyline
storylineStartDateNoISO 8601 start date for the storyline

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

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 must convey behavioral traits. It implies a partial update via 'Pass at least one field to change,' but does not explicitly state that omitted fields retain their values, nor does it mention permissions, side effects, or response format. This is adequate but not rich.

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?

A single sentence, tightly packed with essential information: action, target, editable fields, and invocation requirement. No filler or redundant text.

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?

Given it is a simple metadata update tool without annotations or output schema, the description is mostly complete. It could explicitly say that only provided fields are updated, but 'Pass at least one field to change' conveys that idea. The rich schema fills in the remaining parameter details.

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 input schema provides descriptions for all 7 parameters (100% coverage). The description itself only enumerates some fields and adds no extra syntax or format details beyond what the schema already documents. Baseline 3 is appropriate when schema handles parameter semantics.

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?

Description clearly states the action (Update), the resource (storyline), and the specific metadata fields (title, live status, dates). This distinguishes it from sibling tools like storyline_create, storyline_get, and storyline_delete.

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 provides a clear usage requirement: 'Pass at least one field to change.' This guides the agent on when the tool is appropriate and what input is needed. It does not explicitly list exclusion cases or alternatives, but the context is sufficient.

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

Deploy Server

Other Tools