Skip to main content
Glama

Single-Asset Campaign

adgpt_single_asset
Destructive

Generate a BATCH of premium creatives of one asset type (SAC), or bulk-order N assets in one request (bulk* actions: pricing, order, status, assets, cancel — credits charged upfront, failed items auto-refund) — image: 6 image ads (3 with text + 3 clean) · video: 4 video ads · ugc_action: 3 UGC presenter videos (the way to order UGC videos; named UGC in the app) · ugc_video: only the script-only Talking Actors order (a product ugc_video order is refused 503 REGULAR_UGC_UNAVAILABLE — send ugc_action) · google_ads: 12 ad variations. create → (customize) → confirm. Interactive UGC/in-action uses confirm sub-payloads. pricing / eligibility quote the credit cost first. Talking Actors "Create Variations": variationsQuote (free) says whether a finished Talking Actors video can get 3 new videos of the same actor acting its script in 3 places that fit it, and the exact credits; createVariations spends credits (that figure) and returns the new campaign_id to poll. Any length of source video works: each variation is as long as the video its script makes (its own scenes, each at least 5 s; never the source video's own length) in whole seconds (5-60 s, priced by the second; the quote's duration), and one whose script runs past 60 s gets 60 s variations with the script condensed (the quote says shortened: true). createVariations optionally takes the product — a product photo (product_image_url, from the product-image upload) OR a product page link (product_url, read for the product's name, details and photos), not both — and the brand (brand_id of one of your brands, or no_brand: true; neither keeps the source video's brand, which the quote returns as brand). Actions: pricing, eligibility, create, confirm, cancel, status, assets, regenerateAsset, downloadAll, variationsQuote, createVariations, bulkPricing, bulkOrder, bulkStatus, bulkAssets, bulkCancel. 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_single_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "pricing",
      -  "eligibility",
      -  "create",
      -  "confirm",
      -  "cancel",
      -  "status",
      -  "assets",
      -  "regenerateAsset",
      -  "downloadAll",
      -  "bulkPricing",
      -  "bulkOrder",
      -  "bulkStatus",
      -  "bulkAssets",
      -  "bulkCancel"
      -]New value: +[
      +  "pricing",
      +  "eligibility",
      +  "create",
      +  "confirm",
      +  "cancel",
      +  "status",
      +  "assets",
      +  "regenerateAsset",
      +  "downloadAll",
      +  "variationsQuote",
      +  "createVariations",
      +  "bulkPricing",
      +  "bulkOrder",
      +  "bulkStatus",
      +  "bulkAssets",
      +  "bulkCancel"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnly=false, idempotent=false, so the description earns credit for going beyond them: credits charged upfront, failed items auto-refund, a product ugc_video order is refused with 503 REGULAR_UGC_UNAVAILABLE, variationsQuote is free while createVariations spends credits. It does not say what cancel destroys or whether a confirmed campaign is reversible, which matters given destructiveHint=true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Sentences are extremely long with nested em-dash and parenthetical clauses, and multiple concepts (asset counts, bulk semantics, UGC routing, variations pricing, product/brand params) are packed into two run-on paragraphs. Information is front-loaded but the density makes it hard to scan and the action list appears twice in effect.

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?

Given 16 actions and no output schema, deferring parameter detail to adgpt_capabilities is a reasonable design, and the description covers the tricky paths (UGC action choice, variations quote/spend, product and brand inputs). Still, an agent must make a second call for most actions' parameters, and the destructive behavior of cancel/regenerateAsset is never described.

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

Parameters3/5

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

The schema is nearly empty for the payload — params is a free-form object pointing at adgpt_capabilities — so the description has to carry the load and it only partially does. It names product_image_url vs product_url (mutually exclusive), brand_id / no_brand, and the shortened/duration semantics of variations, but leaves the parameters for pricing, create, confirm, bulk* and the rest undocumented.

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 opening states a concrete verb and resource: generate a BATCH of premium creatives of one asset type, or bulk-order N assets. It then differentiates the asset-type variants (image=6 ads, video=4, ugc_action=3, google_ads=12) so an agent can pick the right mode. The core purpose is clear, though it is buried under a very long enumeration of sub-actions.

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?

Gives real routing guidance: 'ugc_video: only the script-only Talking Actors order ... send ugc_action', 'pricing / eligibility quote the credit cost first', and the create → customize → confirm flow. The variationsQuote-vs-createVariations sequence (free quote first, then spend) is spelled out. It does not compare against sibling tools like adgpt_ugc or adgpt_in_action, so alternatives outside the tool are left implicit.

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