shopify-chatgpt-ads-mcp

Overview Schema Source Related Servers Discussions Admin

Edit campaign settings

update_campaign

Change a campaign's name, description, schedule, targeting, or tracking template without touching its status or budget; targeting you omit stays unchanged.

Instructions

Change name, description, schedule, targeting or tracking template. Never changes status or budget (use pause_campaign, activate_campaign, set_budget). Targeting you do not mention is kept as it is.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "update_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	No
`end_time`	No	ISO 8601, or null to clear
`countries`	No	ISO 3166-1 alpha-2 codes, e.g. ["US"]. location_ids is preferred
`platforms`	No	Omit for every platform
`start_time`	No	ISO 8601, or null to clear
`campaign_id`	Yes	Campaign id
`description`	No
`location_ids`	No	Country, 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
`excluded_location_ids`	No
`query_string_template`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive and open-world, so the safety bar is partly covered. The description goes beyond them by disclosing the patch/merge semantics for targeting and the hard scope boundary around status and budget. It stops short of saying anything about permissions, error/refusal behavior, or the response, which keeps it below a 5.

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

Conciseness5/5

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

Two short sentences, front-loaded with the mutable fields and immediately followed by the boundary and the merge rule. Every clause carries information an agent would otherwise have to guess.

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 10-parameter mutation tool with no output schema, the description covers the essential decision surface: what can change, what cannot, and how partial input behaves. What is missing is minor but real — no mention of what is returned, or of any prerequisite such as fetching the campaign first.

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 only 60%, so the description has to carry weight, and it does: it groups the parameters into named concepts (schedule, targeting, tracking template) and, critically, states that unmentioned targeting is preserved rather than cleared. It does not explain the location_ids versus countries preference or null-clearing behavior, which remains a gap against the partial schema coverage.

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 gives a specific verb (Change) plus an enumerated set of resources (name, description, schedule, targeting, tracking template) and explicitly states what the tool does NOT touch (status, budget). This cleanly separates it from siblings like pause_campaign, activate_campaign and set_budget without the agent needing to open any schema.

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 names the excluded operations and routes them to the exact alternative tools: 'use pause_campaign, activate_campaign, set_budget'. The second sentence adds the key conditional rule for partial edits ('Targeting you do not mention is kept as it is'), so both when-to-use and when-not-to-use are explicit.

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

Deploy Server