shopify-chatgpt-ads-mcp

Overview Schema Source Related Servers Discussions Admin

Preview ad

preview_ad

Read-only

Generates an OpenAI ChatGPT ad preview link so you can show users how a paused ad will appear; the link expires in about 24 hours and does not confirm serving eligibility.

Instructions

A link to OpenAI's own preview of an ad as it would appear in ChatGPT. Works for paused ads; the link expires after about 24 hours. A preview shows appearance only, not serving eligibility. Show the link to the user before any activation.

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": {
      "ad_id": "<ad_id>"
    },
    "name": "preview_ad"
  }
}

Input Schema

Name	Required	Description	Default
`ad_id`	Yes	Ad id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and non-destructive, and the description adds genuinely new behavior: the link expires after ~24 hours, works on paused ads, and shows appearance only rather than serving eligibility. Those are exactly the caveats an agent needs to set user expectations correctly.

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?

Four short sentences, zero filler, with the return value stated first and the expiry and eligibility caveats following. Nothing repeats the annotations or the schema.

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?

With no output schema, the description usefully explains what comes back (a temporary link) and its limits (24-hour expiry, appearance-only, paused-ads support). For a one-parameter read-only tool, nothing material is missing.

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?

The single ad_id parameter is 100% covered by the schema with a pattern constraint, so the schema carries the semantics. The description only refers to 'an ad' generically and adds no format, sourcing, or scoping detail beyond the schema.

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 makes clear this produces a preview link for an ad as rendered in ChatGPT, and distinguishes it implicitly from get_ad by emphasizing appearance rather than data. The verb is slightly buried in the noun phrase 'A link to...', but an agent can still tell what the call yields.

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 gives explicit workflow guidance: 'Show the link to the user before any activation,' and notes it 'Works for paused ads,' which tells the agent the tool is usable in a state where other ad tools might not be. It doesn't name a sibling alternative, but none is obviously needed for a preview-only operation.

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

Deploy Server