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

shopify-chatgpt-ads-mcp

by Avada-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Archive ad group

archive_ad_group
Destructive

Permanently archives an ad group; this cannot be undone, so confirm intent with the user before calling.

Instructions

Archive an ad group. PERMANENT (OpenAI cannot un-archive). Say so to the user before calling.

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": "archive_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_group_idYesAd group id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds information the annotations cannot encode: the operation is permanent and cannot be un-archived. That is the single most consequential fact for the caller and is stated plainly.

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?

Three short fragments arranged in priority order: action, irreversibility, required user-facing step. Nothing is redundant and the critical constraint is front-loaded.

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-parameter destructive tool with no output schema, the essentials are covered: what it does, that it is irreversible, and that the user must be warned. It omits side effects on child entities or the response shape, but those are minor at this complexity.

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?

There is one parameter, ad_group_id, with 100% schema description coverage and a pattern constraint already in the schema. The description adds no format, sourcing, or acceptance detail about the id, so the schema does the work and the baseline 3 applies.

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?

States a specific verb (Archive) and resource (an ad group), clearly distinguishable from siblings like pause_ad_group, update_ad_group, or archive_ad. It does not explicitly name the reversible alternative, which keeps it short of a 5.

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?

Adds a concrete precondition that governs usage: instructs the agent to tell the user this is permanent before calling. That is real when-to-use guidance beyond a generic context statement, but it never mentions pause_ad_group as the reversible option.

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