tool4seller-mcp

Query keyword rank trackers

query_keyword_rank_trackers

Read-only

One trackingScope per request: PARENT (default) uses parentAsin and tracks the family; CHILD uses asin and tracks only that exact variation, excluding siblings. The server resolves its parent. For tracker lists use parentAsins with PARENT or asins with CHILD. Query, ADD, RESUME, REMOVE and SET_COMPETITORS must preserve the same scope and target. Both OWN_PRODUCT and independent COMPETITOR support CHILD. For OWN_PRODUCT associations, PARENT competitorAsins are parent/standalone ASINs while CHILD competitorAsins are exact variation ASINs. includeCompetitors compares the same scope. Account capabilities and notices are returned even for empty results. Check advertisingRankTracking before interpreting advertising ranks or offering advertising tracking. False means unsupported, not a missing match; never promise advertising ranks or silently substitute organic tracking for an explicit advertising-rank request. This applies to own products, independent competitors, and associated competitors. Returns keyword rank tracking configuration across authorized stores. Groups top-level items by storeId and the selected tracking target with nested keywords, and may include PENDING_KEYWORDS parents. Each tracking record has a stable trackingId and its own ACTIVE or PAUSED state. PAUSED means the system stopped tracking due to package expiry or restrictions; it is not a customer pause action. Restore it with RESUME only when package access and quota permit. Returns all matching configuration without pagination. Product title and imageUrl are included when available. Latest rankings are not included; use query_keyword_rank_trends with storeId, parentAsin and keywords to retrieve rankings. This tool does not return Search Volume or calculate rank changes. Query query_account_usages with resources=[KEYWORD_RANK_TRACKING_KEYWORDS] for account quota; list counts are not quota usage. One product type per request: OWN_PRODUCT (default) or independent COMPETITOR. Call separately for each type; ALL and mixed selections are not supported. Competitors share account-wide marketplace/keyword quota with owned products. To create tracking use prepare_keyword_rank_tracking_creation; to resume or archive existing keywords use prepare_keyword_rank_tracking_changes; to replace associated competitors use prepare_keyword_rank_competitor_replacement. Follow each published schema and obtain explicit customer confirmation before its matching apply tool. Preserve the returned trackingScope: PARENT uses parentAsin; CHILD uses asin. Never substitute the parent when a customer requests one child.

Input Schema

Name	Required	Description	Default
`asins`	No	Optional exact child ASIN filters for CHILD only; omit parentAsins.
`states`	No	Optional keyword tracking states. Accepts PENDING_KEYWORDS, ACTIVE, and PAUSED and includes all three when omitted. REMOVED is internal and unavailable.
`keywords`	No	Optional exact tracked keyword filters, up to 20. Multiple values use OR; different filter fields use AND.
`storeIds`	No	Optional store IDs in sellerId:marketplaceId format, up to 100. Omit to query all active authorized stores. Every returned item includes storeId.
`searchText`	No	Optional case-insensitive search. Matches exact parent/child ASIN or a keyword substring within tracked configurations. Search does not match listing titles. Product title and imageUrl are added for matched trackers; ranking history is not queried.
`parentAsins`	No	Optional exact tracked parent ASIN filters, up to 100. For PARENT only; CHILD uses asins instead.
`productType`	No	One product type per request: OWN_PRODUCT (default) or independent COMPETITOR. Call separately for each type; ALL and mixed selections are not supported. Competitors share account-wide marketplace/keyword quota with owned products.	OWN_PRODUCT
`trackingScope`	No	PARENT (default) tracks a parent family using parentAsin. CHILD tracks only the specified variation using asin; omit parentAsin. Never silently substitute a parent or sibling. Applies to OWN_PRODUCT and independent COMPETITOR. SET_COMPETITORS supports both scopes for OWN_PRODUCT: parent/standalone competitors for PARENT, exact child competitors for CHILD.	PARENT

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Rich disclosure beyond the readOnlyHint/non-destructive annotations: PAUSED means system-stopped due to package expiry, not a customer pause; RESUME is conditional on package access; account capabilities and notices return even for empty results; no pagination; advertisingRankTracking=false means unsupported and must not be substituted with organic ranks. The deduction is for spending several sentences on ADD/RESUME/REMOVE/SET_COMPETITORS rules that do not apply to this read-only tool, which can leave an agent unsure what this tool itself performs.

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

Conciseness2/5

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

The core purpose ("Returns keyword rank tracking configuration...") appears roughly 40% into a ~350-word block, behind a scope rule that is then restated three more times, including "Never substitute the parent when a customer requests one child" at both the opening and the close. Material unrelated to a read-only query (ADD/REMOVE/SET_COMPETITORS guidance) consumes budget that matches would be better spent elsewhere.

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

Completeness5/5

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

An output schema exists, yet the description still covers the things an agent must know to call it correctly: empty-result behavior, PENDING_KEYWORDS parents, stable trackingId with independent ACTIVE/PAUSED state, quota sharing between competitors and owned products, and the advertising-rank caveat. Nothing needed for a correct call is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds relational meaning the schema does not spell out: parentAsins pairs with PARENT and asins with CHILD (never both), and for OWN_PRODUCT associations PARENT competitorAsins are parent/standalone ASINs while CHILD ones are exact variations. The repeated "one product type per request" rule is useful only because it clarifies that ALL/mixed selections are rejected.

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?

The description states a specific verb and resource ("Returns keyword rank tracking configuration across authorized stores") and defines the grouping model (by storeId and selected tracking target, with nested keywords). It clearly distinguishes itself from query_keyword_rank_trends for rankings and from prepare_* siblings for creation/changes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It routes explicitly: use query_keyword_rank_trends for latest rankings, query_account_usages for quota, prepare_keyword_rank_tracking_creation/changes/competitor_replacement for mutations. It also states exclusions (no Search Volume, no rank changes, no rankings), which is exactly the when-not guidance an agent needs.

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

All tool4seller-mcp 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.

Resources

Need Help?