Skip to main content
Glama
storelift-mcp

storelift-mcp

Resume Apple Ads campaign (preview)

resume_campaign
Destructive

Resume a paused Apple Ads campaign after explicit user approval; spending restarts once Apple applies the command.

Instructions

PREVIEW ONLY: resume a paused Apple Ads campaign. Spending restarts once Apple applies the command. Apply only with the user's explicit approval.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "resume_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds genuine context beyond that: the call is a preview, and spending restarts only once Apple applies the command, which tells the agent the effect is queued/async rather than immediate. What is missing is any statement of permissions needed or reversibility.

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 clauses, with the preview-only warning and the action front-loaded before the approval caveat. Every sentence carries information the agent needs; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent mutation with no output schema, the definition covers the effect and the approval gate but omits what the call returns and how to check that the command took effect. The presence of get_ads_command_status among siblings suggests a command handle is produced, which the description does not mention. It is adequate but leaves a real operational gap.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry meaning for campaignId. It never mentions the parameter, its expected identifier format, or how to obtain a valid campaign ID (e.g., from get_ads_campaigns). The only mitigating factor is that there is a single, self-descriptively named parameter.

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 (resume) plus the exact resource (a paused Apple Ads campaign), and the 'PREVIEW ONLY' prefix immediately frames what the call does. It is distinguishable from the inverse pause_campaign and from keyword-level siblings by naming the campaign resource. It stops short of an explicit sibling comparison, 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 Guidelines3/5

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

The description carries one hard usage constraint: apply only with the user's explicit approval, which is meaningful gating for an agent. However, it gives no routing guidance between this tool and alternatives such as pause_campaign, resume_keyword, or a confirm_action flow. Usage is implied by the approval rule rather than fully specified.

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