Skip to main content
Glama

ad_group_resume_preview

Read-onlyIdempotent

Preview resuming a single Apple Ads ad group to inspect the outcome before applying the change.

Instructions

Preview resuming one ad group.

Input Schema

NameRequiredDescriptionDefault
idYes
profileYeslocal Apple Ads profile name
adAccountIdYesApple Ads ad account ID

Output Schema

NameRequiredDescriptionDefault
errorNo
previewNo
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which covers the safety and idempotency profile. The description reinforces that this is a preview rather than an actual resume, but it adds little beyond the annotations and does not explain what the preview output allows the caller to do.

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?

The description is a single front-loaded sentence with no filler. It is appropriately concise for a simple preview tool, though its brevity is partly why other dimensions lack guidance.

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?

Given the simple three-parameter schema, annotations, and an output schema, the description is minimally adequate. However, it does not clarify the preview-to-apply workflow, the role of the id parameter, or when this preview should be chosen over sibling preview tools.

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?

Schema coverage is 67%: profile and adAccountId are described in the schema, while id has no schema description. The description's phrase 'one ad group' implicitly identifies id as the ad group identifier, but it adds no format or constraint details 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 states a specific action and resource: previewing the resumption of one ad group. It is clear enough to distinguish this as an ad-group-level preview rather than an ad or campaign preview, but it does not explicitly contrast with siblings such as ad_group_pause_preview or ad_resume_preview.

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 gives no explicit guidance on when to use this preview versus related tools such as ad_group_get, ad_group_update_preview, or operations_apply. The word 'Preview' implies a read-only preflight step, but the description does not state prerequisites, exclusions, or next steps.

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