AMZ Vault

PPC: Campaigns

ppc_campaigns

Read-only

Query campaign performance data with optional filters. Returns campaigns sorted by spend (descending) with metrics: cost, sales, ACoS, clicks, impressions, purchases, CTR, CVR, CPC. Supports filtering by ad type (SP/SB/SD), campaign name, and metric thresholds (acos_min, acos_max, spend_min, etc.). IMPORTANT: When the user asks for campaigns above/below a metric threshold, ALWAYS use the appropriate min/max filter parameter — do NOT just sort and return all campaigns.

Input Schema

TableJSON Schema

Name	Required	Description
`sku`	No	Scope by seller SKU (mapped to ASINs for SB coverage; matches SP/SD ad rows directly).
`asin`	No	Scope to campaigns advertising this ASIN (SP advertised products, SB ad creatives, SD promoted products).
`skus`	No	Scope by multiple seller SKUs.
`sort`	No	Sort field. Default: cost.
`asins`	No	Scope to campaigns advertising ANY of these ASINs.
`limit`	No	Campaigns per page. Default: 25, max: 500.
`offset`	No	Pagination offset — use next_offset from the previous response to page through ALL campaigns.
`ad_type`	No	Filter to a specific ad type. Omit for all types.
`acos_max`	No	Maximum ACoS as decimal (e.g. 0.30 for 30%). Only return campaigns with ACoS <= this value.
`acos_min`	No	Minimum ACoS as decimal (e.g. 0.50 for 50%). Only return campaigns with ACoS >= this value.
`end_date`	No	End date (YYYY-MM-DD). Defaults to today.
`roas_min`	No	Minimum ROAS (e.g. 3.0 for 3x return).
`sales_min`	No	Minimum sales in dollars.
`spend_max`	No	Maximum spend in dollars.
`spend_min`	No	Minimum spend in dollars. Only return campaigns spending at least this amount.
`clicks_min`	No	Minimum clicks.
`parent_sku`	No	Scope to the full family by parent SKU.
`profile_id`	No	Which advertising profile (see account_profiles). Optional when the token has exactly one.
`start_date`	No	Start date (YYYY-MM-DD). Defaults to 30 days ago.
`campaign_id`	No	Filter to a specific campaign ID.
`parent_asin`	No	Scope to the FULL parent family: resolves every child ASIN (product library / Category Listing) and matches campaigns advertising any of them. The response's scope block shows the resolved ASINs.
`period_days`	No	Lookback period in days. Alternative to start_date/end_date. Default: 30.
`impressions_min`	No	Minimum impressions.
`campaign_name_contains`	No	Filter campaigns whose name contains this substring (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already report readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context beyond that: default sort by spend descending, returned metrics, and the crucial rule that threshold queries must use min/max filters rather than relying on sorted output.

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?

The description is compact and front-loaded, with the core purpose stated first and the critical usage warning placed at the end. Every sentence contributes necessary information without redundancy.

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 tool with 24 optional parameters and no output schema, the description provides a solid overview of return values and key usage behavior. It relies on the schema for parameter details, which is appropriate given the 100% schema coverage.

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 description coverage is 100%, so the schema fully documents every parameter. The description reinforces the threshold-filter concept but does not add meaningfully beyond the schema's per-parameter descriptions.

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 clearly states the tool queries campaign performance data and lists the returned metrics, with filtering mentioned. However, it does not explicitly distinguish this from close siblings like ppc_campaign_search or ppc_campaign_details.

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?

The context is clear: this is for querying campaign performance data with optional filters. The IMPORTANT note gives concrete parameter-usage guidance for threshold queries, but it does not contrast this tool with alternatives.

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

All AMZ Vault tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?