Agent Central

Subscribe and Save

get_subscribe_and_save

Read-only

Get Amazon Subscribe & Save offer status, historical snapshots, and Amazon-provided Subscribe & Save metrics.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`skus`	No	Filter metrics by SKU where Amazon supports SKU filters.
`view`	No	Data view. Defaults to offers, or offer_history when start_date/end_date is provided without a view. Use offer_metrics for ASIN/SKU metrics and seller_metrics for seller/brand-level retention and revenue metrics.
`asins`	No	Filter by specific ASINs. Live offers are capped at 20 ASINs per call; metrics support depends on Amazon's view/filter rules.
`limit`	No	Max rows to return (1-500, default 20). Live offers are capped at 100 by Amazon.
`offset`	No	Pagination offset (0-100000, default 0). Use the returned pagination.next_offset to continue.
`metrics`	No	Optional Amazon metric allowlist for seller_metrics. Omit for Amazon's default/all metrics unless using ASIN/SKU/fulfillment filters.
`end_date`	No	Optional. YYYY-MM-DD. Defaults to today for offer_history and metrics views.
`start_date`	No	Optional. YYYY-MM-DD. For offer_history, reads stored snapshots. For metrics views, defaults to a 30-day window ending at end_date/today.
`brand_names`	No	Filter seller_metrics by brand name where Amazon supports brand filters. Retention metrics are brand-filterable for US marketplace data.
`include_raw_rows`	No	False returns compact rows. Default true.
`time_period_type`	No	Metrics period type for offer_metrics and seller_metrics.	PERFORMANCE
`include_diagnostics`	No	True may add expanded freshness diagnostics. Basic empty-result data-window diagnostics are included by default when available.
`aggregation_frequency`	No	Metrics aggregation frequency for offer_metrics and seller_metrics.	WEEK
`fulfillment_channel_types`	No	Filter metrics by fulfillment channel type where supported.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`evidence`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026

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, and openWorldHint=true, so the safety profile is covered. The description adds that results include historical snapshots and Amazon-provided metrics, but says nothing about pagination behavior, freshness, or the 20-ASIN/100-offer caps that materially affect calls – although those appear in the schema rather than the description.

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?

A single front-loaded sentence with no filler. It is efficient, though at the cost of being thin for a tool with 14 parameters and four view modes.

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?

With an output schema present, return values need not be explained, and full schema coverage handles the parameters. However, for a 14-param, zero-required, four-view tool, the description does little to orient an agent on which view to pick or that this is a read-only reporting tool rather than a mutation.

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 every one of the 14 parameters is already documented in the schema, and the baseline is 3. The description adds no parameter-level meaning beyond repeating 'offer status, historical snapshots, metrics' at a high level.

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 (Get) and resource (Amazon Subscribe & Save) plus the three categories of data returned (offer status, historical snapshots, metrics). It is clear what the tool does, but it makes no attempt to distinguish itself from the many other get_* siblings or to signal that it is the sole Subscribe & Save surface.

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 offers no when-to-use guidance, no prerequisites, and no alternatives. The existence of four views (offers, offer_history, offer_metrics, seller_metrics) is the key usage decision, yet it is only explained inside the schema, not the description.

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

All Agent Central tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.