Skip to main content
Glama
Sign In
shopify-chatgpt-ads-mcp

shopify-chatgpt-ads-mcp

by Avada-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Create campaign (paused)

create_campaign

Creates a paused OpenAI ads campaign with a set budget, targeting, and objective so you can review and activate it later without immediate spend.

Instructions

Create a campaign. It is ALWAYS created paused and spends nothing until activate_campaign. Budget is in the ad account currency (get_ad_account); daily is required for Maximize clicks/conversions. A product-feed (Shopping) campaign needs product_feed_id; its feed, objective and mode cannot change later. Daily minimums depend on the currency and OpenAI states them when it refuses. Identical requests return the same campaign (Idempotency-Key).

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": {
      "name": "<name>",
      "budget_type": "<budget_type>",
      "budget_amount": "<budget_amount>"
    },
    "name": "create_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
end_timeNoISO 8601
countriesNoISO 3166-1 alpha-2 codes, e.g. ["US"]. location_ids is preferred
objectiveNoDefault clicks
platformsNoOmit for every platform
start_timeNoISO 8601; omit to start when activated
budget_typeYes
descriptionNo
location_idsNoCountry, region or market ids from search_locations. An account can target only the countries OpenAI allows it; none are listed anywhere, a refusal says so
budget_amountYesBudget, in major units of the ad account currency, e.g. "50" or "12.50"
product_feed_idNoFeed id for a product-feed (Shopping) campaign
excluded_location_idsNo
query_string_templateNoTracking parameters, e.g. utm_source=chatgpt&utm_medium=cpc&utm_campaign={campaign_id}. Never oppref (OpenAI adds it)
conversion_event_setting_idNoRequired for objective conversions (list_conversion_event_settings)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only flag it as a non-read, non-destructive, open-world write; the description adds the consequential traits an agent cannot infer: the campaign is created paused and spends nothing, feed/objective/mode are immutable after creation, identical requests are deduplicated via Idempotency-Key, and budget minimums surface as refusals rather than validation errors.

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?

A single front-loaded block that leads with the most surprising fact (always created paused) and then covers budget, feed immutability, minimums, and idempotency in order of likely relevance. Density is high and the phrasing around minimums/refusals is slightly convoluted, but no sentence is filler.

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 14-parameter mutation with no output schema, the description covers the failure modes that matter: currency mismatch, missing daily budget, missing feed id, immutable fields, and duplicate submissions. It never says what a successful call returns (presumably a campaign id used by get_campaign/activate_campaign), which is the main remaining gap.

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 71%, and the description adds genuinely new semantics on top: budget_amount is denominated in the ad account currency (from get_ad_account), budget_type=status daily is mandatory for certain objectives, and product_feed_id is mandatory for Shopping. It does not explain excluded_location_ids or the countries-vs-location_ids preference beyond what the schema already says.

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 description opens with a specific verb and resource ('Create a campaign') and immediately scopes it as always paused, which distinguishes it from update_campaign and activate_campaign. It stops short of naming any sibling explicitly as the wrong tool for a given job, but the resource creation intent is unambiguous.

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 clear conditional guidance: activation is required before spend ('spends nothing until activate_campaign'), daily budget is required for Maximize clicks/conversions, and a Shopping campaign requires product_feed_id. Prerequisites for currency and conversion event settings are delegated to get_ad_account and list_conversion_event_settings. No explicit 'do not use when' exclusion is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools