Skip to main content
Glama

Create Ads Campaign

create_ads_campaign
Destructive

[write] Create an ad campaign draft (ad account by ads_account_id or ads_account_uuid, website by seliee_website_id or seliee_website_uuid; the result has the campaign's id and uuid) and publish it to the provider PAUSED (it cannot spend until activate_ads_campaign). Goal: META MESSAGES/TRAFFIC, GOOGLE SEARCH or VIDEO (promote a YouTube video: creative {youtube_video_id - an id or a YouTube url, business_name, headlines, long_headlines, descriptions, logo_image_url (https square image) or logo_asset}; runs on YouTube in-stream, in-feed and Shorts), LINKEDIN/TWITTER TRAFFIC/AWARENESS/ENGAGEMENT, OPENAI TRAFFIC/AWARENESS, SNAPCHAT/REDDIT TRAFFIC/AWARENESS, APPLE TRAFFIC (creative.adam_id required), MICROSOFT SEARCH. Budget is daily, in the account currency. Targeting/creative follow enums/ads_campaigns.py (e.g. Google needs keywords, headlines, descriptions; Meta needs a page; TIKTOK (goal TRAFFIC or AWARENESS) needs creative {video_id: tt_video_id from list_tt_videos, tt_account_id}). META creative: a new ad {page_key, message, headline?, image_url?}, or boost an existing page post {page_key, post_key} (list_ads_meta_posts), or promote an Instagram post {page_key, instagram_user_key, instagram_media_key}. A failed provider publish keeps the draft; retry with publish_ads_campaign.

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": {
      "ads_campaign_title": "<ads_campaign_title>",
      "ads_campaign_goal": "<ads_campaign_goal>",
      "ads_campaign_daily_budget": "<ads_campaign_daily_budget>"
    },
    "name": "create_ads_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
ads_account_idNo
ads_account_uuidNo
ads_campaign_goalYes
seliee_website_idNo
ads_campaign_titleYes
seliee_website_uuidNo
ads_campaign_creativeNo
ads_campaign_end_dateNo
ads_campaign_targetingNo
ads_campaign_custom_urlNo
ads_campaign_start_dateNo
ads_campaign_daily_budgetYes

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 non-readonly, destructive, open-world, non-idempotent, so the safety bar is partly covered; the description adds real value by explaining that the provider publish lands PAUSED and cannot spend until activation, and that a failed publish keeps the draft for retry. It does not explain what the destructiveHint covers, auth/account requirements, or whether a duplicate call creates a second campaign.

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

Conciseness3/5

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

The front-loaded first clause is good, but the rest is one enormous sentence built from nested parentheses, comma-separated platform lists, and inline dict literals, which makes it hard to scan. Much of the provider-specific detail earns its place, yet the structure works against comprehension and could be broken into a short purpose line plus per-provider notes.

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?

For a 12-parameter, open-world mutation with no output schema and no schema-level descriptions, the description covers a lot of the risky surface: creative shape, budget units, paused-publish state, failure retention. It still leaves the targeting object, date fields, and custom URL undefined, deferring to an external Python module an agent cannot read.

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 0% across 12 parameters, so the description must carry the load, and it does explain the id-or-uuid pattern for the account/website, that budget is daily in account currency, and the per-provider creative shapes. However ads_campaign_targeting is dismissed with a pointer to an external source file ("targeting follow enums/ads_campaigns.py"), and start/end date and custom_url are never mentioned at all.

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 an ad campaign draft") and immediately disambiguates scope: draft creation plus a PAUSED provider publish, not activation (activate_ads_campaign) or retry (publish_ads_campaign). It also enumerates which ad platforms/goals are supported, so an agent can tell it apart from create_ads_campaign_from_audience or edit_ads_campaign without opening the schema.

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?

It states the create-then-activate flow explicitly ("cannot spend until activate_ads_campaign") and gives a recovery path ("retry with publish_ads_campaign"), plus points to prerequisite lookups like list_tt_videos and list_ads_meta_posts. What it lacks is a direct comparison to the closest sibling, create_ads_campaign_from_audience, or any statement about when to use edit_ads_campaign instead.

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.