Skip to main content
Glama

Social Media MCP by Publinio

prepare_product_beautifier_automation

Idempotent

Save an inactive review draft. Does not generate content, spend credits or publish. Only enhanced product 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>",
      "recipe": "<recipe>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "prepare_product_beautifier_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipeYes
brandIdYes
idempotencyKeyYes

Output Schema

NameRequiredDescriptionDefault
automationYes

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 cover the safety profile (readOnly=false, destructive=false, idempotent=true, openWorld=false), so the bar is lower; the description still adds real value by disclosing that this saves an inactive draft, spends no credits, produces no content, and does not publish. It does not describe what lifecycle state the draft lands in or whether it can be re-saved, but the behavioral additions go beyond the 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 short sentences, the key constraint (inactive draft, no credits, no publish) front-loaded, with no padding. The trailing semicolon clause "Only enhanced product images; the saved automation type must match this tool" is compressed to the point of ambiguity, which slightly dents clarity.

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 safety annotations are present. But for a tool whose input is a large nested recipe with zero schema descriptions, the definition leaves an agent without enough to construct the payload correctly — it should at least point at what the recipe and attachmentIds represent.

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 three top-level parameters and a deeply nested recipe object (configuration, attachmentIds, generationWeekdays, caps, etc.), and the description supplies no parameter meaning at all — not even the role of idempotencyKey or the attachment requirements. With low coverage and high schema complexity, the description needed to compensate and does not.

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?

"Save an inactive review draft" gives a clear verb and output state, and "Only enhanced product images" scopes the resource to the product-beautifier domain, which separates it from the many sibling prepare_* tools. However, the description never says "automation" as the saved resource directly (only obliquely via "the saved automation type must match this tool"), so the resource is inferred rather than stated.

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?

"Does not generate content, spend credits or publish" usefully rules out the generate_*_sample and activate_* paths and signals this is the non-executing save step. But it never names those alternatives or states the positive precondition for using this tool instead of update_product_beautifier_automation or activate_product_beautifier_automation, so the routing guidance is only implied.

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