Skip to main content
Glama
Sign In

Logimu

by com.logimu
OverviewDiscussionsAdmin

product_keywords

Read-onlyIdempotent

REVERSE ASIN on Amazon (11 marketplaces, country): every observed keyword (head search terms taken from Amazon's own autocomplete, page 1 observed about once a week) whose latest page 1 shows the product, organically with its rank or in a sponsored unit present in the page HTML, with the keyword's result count, the Overall Pick badge and the date; organic first, best rank first, with totals (keywords, organic, top 10, sponsored, Overall Pick). Pass asins (up to 10, the product first) to COMPARE it with competitors: each keyword row adds every competitor's organic rank, asins_on_page and gap (a competitor on page 1 organically, the product not); gaps=true keeps only those. history=true adds the first product's rank on each keyword over time. USE WHEN the user asks which keywords a product (theirs or a competitor's) shows up for, where competitors are visible and they are not, or how a product's position on a term moved. Coverage is head search terms and page 1 only, so a product shows fewer keywords than a full search index would. NOT volume figures and NOT live: dated weekly samples. A product not seen on any observed page is free (asin_not_found). COST: paid plan required (listed only for keys on a paid plan); 1 credit per 25 keywords returned per ASIN compared (+0.5 with history when a keyword has more than one observation). Counts against the derived daily cap (default 2,000 calls per account).

Input Schema

NameRequiredDescriptionDefault
asinNoA 10-character Amazon ASIN: the keywords it shows up for. Give asin OR asins.
gapsNoWith asins: only the keywords where a competitor is on page 1 organically and the first product is not.
asinsNoUp to 10 ASINs, the product first, then the competitors to compare it with.
limitNoKeywords per answer (1 credit per 25 returned, per ASIN).
offsetNoSkip this many keywords (paging).
countryNoAmazon marketplace: us (amazon.com, default), uk, de, ca, au, fr, it, es, jp, mx or br, each searched in its own language. us and uk are read in full about weekly; the other nine started 2026-10-29 / 10-30 and fill in week by week (coverage says how far).us
historyNoAlso return the first product's rank on each keyword in every observation; +0.5 credit when a keyword has more than one.
placementNoOrganic and sponsored (default), organic only, or sponsored only.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"us (amazon.com) or uk (amazon.co.uk): the marketplaces the map covers."New value: +"Amazon marketplace: us (amazon.com, default), uk, de, ca, au, fr, it, es, jp, mx or br, each searched in its own language. us and uk are read in full about weekly; the other nine started 2026-10-29 / 10-30 and fill in week by week (coverage says how far)."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "us",
-  "uk"
-]New value: +[
+  "us",
+  "uk",
+  "de",
+  "ca",
+  "au",
+  "fr",
+  "it",
+  "es",
+  "jp",
+  "mx",
+  "br"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Amazon US only: the map covers amazon.com search."New value: +"us (amazon.com) or uk (amazon.co.uk): the marketplaces the map covers."
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "us"
-]New value: +[
+  "us",
+  "uk"
+]
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond that: weekly sampling cadence, page-1-only coverage, the free asin_not_found outcome, credit pricing (1 per 25 keywords per ASIN, +0.5 with history), and the daily cap. Missing is any statement about pagination limits or the shape/ordering of the returned totals, though ordering is partly described.

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?

It is front-loaded with the core definition and then layered with USE WHEN, coverage caveats, and COST, so an agent can stop reading early. The single dense paragraph is long and parenthetical-heavy, which slows scanning, but nearly every clause carries decision-relevant information.

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?

For an 8-parameter, no-output-schema tool this is unusually complete: it covers scope limits, cost accounting, paid-plan gating, a free failure case, ordering, and the comparison/history modifiers. An agent has everything needed to decide whether to call it and what the results mean.

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 the baseline is 3; the description earns more by explaining the comparison semantics behind asins ("the product first", competitor organic rank, asins_on_page, gap) and the exact effect of gaps=true and history=true. The country coverage caveat (us/uk weekly vs. nine markets filling in) also adds meaning the enum alone does not convey.

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?

"REVERSE ASIN on Amazon (11 marketplaces, country): every observed keyword ... whose latest page 1 shows the product" gives a specific verb-equivalent, resource, and scope. It distinguishes itself from sibling keyword tools by defining the reverse-lookup direction and by noting the organic-vs-sponsored distinction and result ordering.

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?

The "USE WHEN" block names three concrete user intents (which keywords a product ranks for, where competitors appear and it does not, how a position moved), and the "NOT volume figures and NOT live" exclusions plus the "COST: paid plan required" prerequisite prevent the main misuses. Alternative routing is implicit via the cost/coverage framing rather than named siblings, but the when/when-not coverage is explicit.

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

All Logimu toolsInspect
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