Skip to main content
Glama

Ad clone

adgpt_recreation

Clone any existing ad: ingest it (URL or upload), analyze its hooks, script and scene structure, then generate your own version from one instruction (adGenerateFromPrompt). Poll adStatus; adCancel refunds an in-flight clone. Actions: adIngestUrl, adUpload, adAnalyze, adStatus, adGenerateFromPrompt, adCancel, adAssets. Call adgpt_capabilities with the operationId to see an action's parameters.

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": {
      "action": "<action>"
    },
    "name": "adgpt_recreation"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, non-idempotent; the description adds substantive facts beyond that: the operation is asynchronous (poll adStatus), cancelling refunds an in-flight clone (implying a paid credit), and per-action parameters live behind adgpt_capabilities. It omits auth requirements, rate limits, and what happens to partially generated assets.

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?

Front-loaded with the workflow in one sentence, then the operational notes, then a routing pointer — no filler. The bare list of seven action names largely duplicates the schema enum, which is the one wasteful element, though it does keep the description self-contained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-action multiplexed tool with a nested params object and no output schema, the description supplies the workflow, the async/polling model, the refund semantics, and an explicit pointer to adgpt_capabilities for per-action parameters. What is missing is what adAssets does and any hint about return payloads or job durations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% and the seven enum values carry no per-value documentation in the schema, so the description must compensate — and it largely does, characterizing adIngestUrl, adUpload, adAnalyze, adStatus, adGenerateFromPrompt and adCancel. adAssets is listed with no meaning at all, and the nested params object is delegated wholesale to adgpt_capabilities, which caps it below 5.

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?

"Clone any existing ad" is a precise verb+resource, and the pipeline (ingest URL/upload → analyze hooks, script, scene structure → generate your own version) makes the scope concrete. It falls short of a 5 because it never contrasts itself with plausibly overlapping siblings such as adgpt_edit_creative, adgpt_ugc, or adgpt_single_asset, so an agent must still infer which generation tool fits.

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

Usage Guidelines4/5

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

The description gives an explicit operating sequence: ingest first, analyze, then adGenerateFromPrompt, then poll adStatus, with adCancel as the escape hatch that refunds. It does not say when to prefer this tool over the other creative-generation siblings, so there is no exclusion guidance, only positive-path guidance.

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