Skip to main content
Glama

ADS Beast

create_campaign_draft

Create a campaign as a DRAFT in the ADS Beast builder: type, geo, languages, daily budget, ad groups with keywords or audiences, ad texts, landing page. Nothing reaches the ad platform. Returns the draft id, builder_url and what still blocks publishing (platform limits, ad policy, compliance); a draft with problems is still saved for update_campaign_draft. Publishing: prepare_campaign_draft_publish or a person in the builder, always paused. Call list_campaign_types first.

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": {
      "client_id": "<client_id>",
      "platform": "<platform>",
      "campaign_type": "<campaign_type>",
      "name": "<name>"
    },
    "name": "create_campaign_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoCountry codes ('UA', 'SK'); Google also takes 'City, CC'. Meta takes country codes only.
nameYesCampaign name a person will see in the builder.
extraNopage_id, instagram_actor_id, dsa_beneficiary, dsa_payor, structured_snippets, search_partners, display_network, geo_target_type, vertical, devices, job_titles, industries, cities, regions.
notesNoA note for the person who will review the draft: what it is for and what to check.
audienceNoSocial types: age_min, age_max, genders, interests, placements, custom_audiences, allow_broad_audience + broad_audience_reason.
platformYes
ad_groupsNoAd groups (ad sets) with their keywords and ads. The exact fields and limits per type are in list_campaign_types.
client_idYesClient id from list_clients.
languagesNoLanguage codes of the audience ('uk', 'en').
conversionNoMeta leads/sales: {type: 'website', pixel_id, event} or {type: 'lead_form', lead_form_id}.
target_cpaNoTarget cost per result in the account currency, when the strategy needs one.
landing_urlNohttps landing page used for every ad that has no final_url of its own.
target_roasNo
bid_strategyNoSee default_bid_strategies of the type in list_campaign_types; empty keeps the platform default.
daily_budgetNoPer day, in the currency of the client's ad account.
campaign_typeYesType key from list_campaign_types, for example google.search or meta.leads_website.
negative_keywordsNoCampaign-level negative keywords (search types).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, openWorldHint=true; the description adds far more, namely that no external platform call occurs, that a defective draft is still persisted, what the response contains (draft id, builder_url, blocking issues from platform limits, ad policy, compliance), and that publishing is always paused. This is exactly the behavioral context an agent needs before invoking a large mutation.

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?

The critical facts (draft-only, nothing reaches the platform, call list_campaign_types first) are front-loaded, and the four sentences are dense but purposeful. The parenthetical field lists and the blocking-issue enumeration make it slightly heavy, though nothing is truly wasted.

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

Completeness5/5

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

For a 17-parameter tool with nested ad_groups and no output schema, the description still covers the return shape (draft id, builder_url, blocking reasons) and the persistence behavior. Combined with 88% schema coverage and the annotations, an agent has everything needed to call it correctly.

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 description coverage is 88%, so the schema already explains geo, audience, ad_groups, conversion, bid_strategy and the rest. The description only restates the field categories and points to list_campaign_types for per-type field and limit detail, adding little format or constraint meaning beyond the structured data. Baseline 3 applies.

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?

The description opens with a specific verb and resource ('Create a campaign as a DRAFT in the ADS Beast builder') and enumerates the content it carries (type, geo, languages, budget, ad groups, ads, landing page). It is clearly distinguishable from prepare_campaign_draft_publish and update_campaign_draft, which are both named.

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

Usage Guidelines5/5

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

It states an explicit prerequisite ('Call list_campaign_types first'), an explicit exclusion ('Nothing reaches the ad platform'), and routes the agent to the correct alternatives for publishing and for fixing a saved draft with problems. When-to-use, when-not-to-use, and alternatives are all present.

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.