Skip to main content
Glama
storelift-mcp

storelift-mcp

Resume Apple Ads keyword (preview)

resume_keyword
Destructive

Resume a paused Apple Ads keyword to restart its spending only after explicit user approval; the preview command takes effect when Apple processes it.

Instructions

PREVIEW ONLY: resume a paused Apple Ads keyword. Spending on it 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>",
      "keywordId": "<keywordId>"
    },
    "name": "resume_keyword"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordIdYes
campaignIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds real value beyond them: spending resumes (a financial consequence) and the effect is deferred until Apple applies the command, which explains the preview semantics that annotations cannot express.

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

Conciseness4/5

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

Three short clauses, front-loaded with the PREVIEW ONLY constraint and the approval requirement, with no filler. Tight and well ordered.

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?

As a mutating, open-world, non-idempotent tool with no output schema and undocumented parameters, it should say what happens next – how to verify the resume took effect or which confirm/status sibling to call. The financial impact and deferral are covered, but the post-call path is left to inference.

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% and the description says nothing about campaignId or keywordId – no format, no source (e.g., from get_ads_keywords), no indication of whether keywordId is globally unique. With two undocumented parameters the description needed to compensate and does not.

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?

States a specific verb and resource with its precondition: resume a paused Apple Ads keyword. That distinguishes it cleanly from resume_campaign (campaign-level) and pause_keyword (opposite direction), so an agent can select it without opening 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 Guidelines4/5

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

Gives an explicit gating condition – apply only with the user's explicit approval – and flags the operation as PREVIEW ONLY. It does not name any alternative or follow-up path (e.g., confirming the action or polling command status), which is the only missing piece.

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