Skip to main content
Glama

Full Campaign

adgpt_campaigns
Destructive

Generate and manage Full Campaigns (FC) from a product URL, a manual product (name+description+images), or text-only. Each campaign generates (defaults): 6 image ads (3 with text + 3 clean), 4 video ads, 3 UGC presenter videos, 12 Google ad copy variations, 10 keywords, plus social captions. Tier (base/pro/premium) changes credit cost and UGC render quality, not asset counts. Re-render one image (regenerateAsset, credits only), download, or remove a campaign from your library. Actions: eligibility, create, status, assets, downloadAll, regenerateAsset, deleteFromLibrary. 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_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description adds genuinely new behavioral context: tier changes credit cost and UGC render quality but not asset counts, and regenerateAsset consumes credits while re-rendering only one image. It falls short of stating whether deleteFromLibrary is recoverable or how long a create takes to complete.

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?

Opening sentence establishes scope immediately, followed by the asset bundle, tier caveat, and action list in descending priority. The final action enumeration largely restates the schema enum, which is the one redundant block in an otherwise dense and well-ordered description.

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 complex multi-action generation tool with no output schema, the description covers input sources, default outputs, cost-tier behavior, and where to find action parameters. The remaining gap is operational: nothing is said about async job behavior or what status/assets return, which matters given the sibling adgpt_job tool.

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?

Schema coverage is 50% and the free-form params object is opaque, so the description must compensate; it partially does by naming the actions and explaining that some take an operationId documented elsewhere. It still gives no hint about which params an action like create or regenerateAsset accepts, leaving the agent dependent on a second tool call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Generate and manage Full Campaigns") and enumerates the three input sources (product URL, manual product, text-only) plus the exact default asset bundle. The scope is concrete enough that an agent can tell it apart from sibling tools like adgpt_single_asset or adgpt_ugc, which produce individual assets rather than a full bundle.

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?

The description lists the seven supported actions and routes the agent to adgpt_capabilities for per-action parameters, which is useful routing. However, it never says when to choose a Full Campaign over adgpt_single_asset, adgpt_recreation, or adgpt_ugc, nor when an action like eligibility should be called before create. Usage is implied by the action list rather than guided.

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