Skip to main content
Glama

Social Media MCP by Publinio

resume_story_creator_automation

DestructiveIdempotent

Resume recurring generation using the saved recipe and credit caps. Previously approved automatic delivery can publish to connected channels. Only vertical story artwork; the saved automation type must match this tool.

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": {
      "brandId": "<brandId>",
      "automationId": "<automationId>",
      "revision": "<revision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "resume_story_creator_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdYes
revisionYes
automationIdYes
idempotencyKeyYes

Output Schema

NameRequiredDescriptionDefault
runNo
automationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered. The description adds meaningful context beyond that: resumption consumes 'credit caps' and 'Previously approved automatic delivery can publish to connected channels,' disclosing the external side effect that explains the openWorld/destructive flags, plus the vertical-story-artwork restriction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the action and its side effect, with the type-matching constraint as a closing guard. Every sentence carries a distinct piece of information; no filler.

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?

An output schema exists so return values need no explanation, and the annotations plus the side-effect disclosure cover behavior reasonably well. The remaining hole is the entirely undocumented required parameter set, including the optimistic-concurrency and idempotency semantics, which matters for a destructive, credit-consuming mutation.

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?

Schema description coverage is 0% and all four parameters are required, yet the description never mentions brandId, automationId, revision, or idempotencyKey. It does not explain that revision guards against stale-state conflicts or that idempotencyKey prevents duplicate resumptions — the two parameters an agent is most likely to get wrong. The description fails to compensate for the total coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource ('Resume recurring generation using the saved recipe') and scopes it with 'Only vertical story artwork; the saved automation type must match this tool,' which distinguishes it from the sibling resume_* tools. It is clear what the tool does, though it does not explicitly name activate_story_creator_automation or prepare_story_creator_automation as the adjacent alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied — resuming a previously saved/paused story automation — and the constraint that 'the saved automation type must match this tool' gives a selection precondition. However, there is no explicit when-to-use versus when-not-to-use guidance, nor any comparison to activate_* or prepare_* siblings that an agent must choose between.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources