Skip to main content
Glama

Social Media MCP by Publinio

resume_ugc_storyboard_automation

DestructiveIdempotent

Resume recurring generation using the saved recipe and credit caps. Previously approved automatic delivery can publish to connected channels. Only UGC storyboard frames; 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_ugc_storyboard_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 disclose destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: resuming reuses the saved recipe and credit caps, and previously approved automatic delivery may publish to connected channels, surfacing a side effect an agent could not infer from annotations alone.

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 dense sentences with the action front-loaded and no filler. The scoping constraint is placed last, which is fine, though the jump between recipe/credits, delivery, and type matching is a bit compressed.

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 cover the safety profile. However, for a four-parameter mutation that consumes credits and can publish to external channels, the complete absence of parameter semantics (especially revision and idempotencyKey) leaves a real gap for correct invocation.

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% across four required parameters, and the description explains none of them. It hints at 'the saved automation type' (automationId) but says nothing about brandId, the revision/concurrency guard, or the required idempotencyKey, leaving the agent to guess at these required inputs.

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?

States a specific verb-plus-resource ('Resume recurring generation using the saved recipe and credit caps') and explicitly scopes it to UGC storyboard frames, which separates it from the ~20 sibling resume_* tools. The phrase 'recurring generation' is slightly abstract, but the type-matching clause pins the resource down.

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?

The description implies usage (resume a previously prepared/paused UGC storyboard automation) and gives a precondition ('the saved automation type must match this tool'), but never states when to choose this over pause_automation or the activate_*/prepare_* siblings. Guidance is implied rather than explicit.

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