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

shopify-chatgpt-ads-mcp

by Avada-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Pause ad group

pause_ad_group

Pause an ad group to stop its ads from delivering without deleting it, letting you halt spend or make changes safely with no confirmation required.

Instructions

Pause an ad group. Safe; no confirmation needed.

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_group_id": "<ad_group_id>"
    },
    "name": "pause_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_group_idYesAd group id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and readOnlyHint=false; the description adds a useful operational note (no confirmation prompt needed), which is real value beyond the structured fields. However, it omits that openWorldHint=true means the pause affects live ad delivery, and it doesn't say whether pausing is reversible or idempotent when the ad group is already paused.

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, the purpose front-loaded before the safety note, with no filler or repetition. Every clause carries information the agent can act on.

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 single-required-parameter mutation with full schema coverage, no output schema, and annotations covering the safety profile, the description is nearly sufficient. The one gap is qualified safety: with openWorldHint=true, "Safe" would be clearer if it stated that the pause is reversible and takes effect on live delivery.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter (ad_group_id) exists and its schema description coverage is 100%, so there is nothing meaningful left for the description to explain. The description adds no parameter detail, but the schema fully documents it.

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?

"Pause an ad group" gives a specific verb and resource, which cleanly separates it from pause_ad, pause_campaign, and archive_ad_group at the name/verb level. It stops short of an explicit contrast with those siblings, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

The description says the call is "safe" and needs no confirmation, which is invocation guidance rather than selection guidance. It never says when to pause versus archive_ad_group, update_ad_group, or pause_ad, leaving the agent to infer the choice from tool names alone.

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