Skip to main content
Glama

Social Media MCP by Publinio

resume_recolor_automation

DestructiveIdempotent

Resume recurring generation using the saved recipe and credit caps. Previously approved automatic delivery can publish to connected channels. Only recolored source images; 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_recolor_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 destructiveHint=true, idempotentHint=true, and openWorldHint=true, but the description adds value beyond them: it discloses that previously-approved automatic delivery can publish to connected channels and that generation consumes credit caps. That side-effect detail (external publishing) is exactly the kind of behavior an agent needs and is not captured by annotations.

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 followed by the two most important constraints (publishing side effect, recolor-type restriction). No filler, though the phrase 'recurring generation' is slightly jargon-heavy.

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 mutation/publishing behavior is covered. The gap is the four undocumented required parameters (notably revision and idempotencyKey) that an agent must supply blindly on a destructive, credit-consuming call.

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 (brandId, automationId, revision, idempotencyKey) are required, yet the description explains none of them. It mentions 'saved recipe' and 'credit caps' but never clarifies revision semantics (optimistic concurrency) or the purpose of idempotencyKey, so the description fails to compensate for the zero-coverage schema.

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 ('Resume') plus the resource ('recurring generation using the saved recipe') and scopes it to recolored source images. The clause 'the saved automation type must match this tool' implicitly distinguishes it from the many other resume_* siblings, though it never names a sibling outright.

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 by the name and the precondition that the automation must already exist, be paused, and be of the recolor type. However, it never states when to prefer resume over activate/update, nor the prerequisite state needed (e.g., a paused automation from pause_automation).

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