Skip to main content
Glama

Social Media MCP by Publinio

resume_reel_concepts_automation

DestructiveIdempotent

Resume recurring generation using the saved recipe and credit caps. Previously approved automatic delivery can publish to connected channels. Only written reel concepts; 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_reel_concepts_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, so the safety profile is covered. The description adds genuinely new behavioral context: that resume consumes credit caps, that previously approved automatic delivery can publish to connected channels (an external side effect), and that the saved automation type must match this tool. It stops short of describing what happens on a revision mismatch or the credit-cap failure mode.

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 short sentences, front-loaded with the action and scoped immediately after; the machine-oriented constraint sits last where it belongs. The fragment 'Only written reel concepts' is clipped enough to be slightly ambiguous, but nothing is padded.

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 not be explained, and the destructive/publishing behavior is disclosed. However, for a destructive, idempotent, four-required-parameter mutation with zero schema descriptions, the definition leaves parameter semantics and sibling routing unaddressed, which is only minimally sufficient.

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, so the description must compensate and it largely does not. brandId, automationId, revision and idempotencyKey are never explained; the concurrency role of 'revision' and the deduplication role of 'idempotencyKey' are exactly the kind of semantics an agent needs and they are missing.

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 and resource ('Resume recurring generation using the saved recipe and credit caps') and adds a scoping clause ('Only written reel concepts; the saved automation type must match this tool') that separates it from the image-oriented resume_* siblings. It does not, however, distinguish itself from the closely related activate_reel_concepts_automation or prepare_reel_concepts_automation, which an agent would need to pick between.

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?

Use is implied by 'Resume' (i.e., restart something previously paused) but never stated, and no alternative is named. With activate_*, prepare_*, pause_automation and update_* all present as siblings, the absence of any routing guidance between them is a real gap.

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