Skip to main content
Glama
Sign In

Logimu

by com.logimu
OverviewDiscussionsAdmin

keyword_rankings

Read-onlyIdempotent

Page 1 of Amazon search for a keyword, as Logimu last OBSERVED it (head search terms taken from Amazon's own autocomplete, each observed about once a week, all departments; amazon.com from one US delivery ZIP): the organic order with product facts (title, brand, price, rating) and each product's latest observed buy box (seller, AMZ / FBA / FBM, other sellers), the sponsored units present in the page HTML (Sponsored Brands banners and videos, server-rendered Sponsored Products; ones Amazon loads later by JavaScript are counted as slots only), the Overall Pick (Amazon's Choice) holder, Amazon's result count, page_summary (organic slots by brand and by buy-box seller, Amazon's own buy boxes, FBA / FBM, Sponsored Brands units by brand) and the products that entered or left page 1 since the previous observation, all dated. history=true adds every weekly observation and the rank series of the page's products. USE WHEN the user asks which products, brands or sellers hold page 1 for a search term, who advertises on it, or how the page changed. All 11 Amazon marketplaces (country). NOT volume figures (Amazon publishes none for search terms and none is implied) and NOT live: a dated weekly sample, and the same search minutes apart differs by a few products - for a live page use the serp tool, for what Amazon suggests for a seed the keywords tool, for the keywords a product shows up for product_keywords. A keyword outside the observed set is free (keyword_not_found). COST: paid plan required (listed only for keys on a paid plan); 1 credit (+0.5 with history when more than one observation exists). Counts against the derived daily cap (default 2,000 calls per account).

Input Schema

NameRequiredDescriptionDefault
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 every weekly observation and the products' rank series; +0.5 credit when more than one exists.
keywordYesA search term, e.g. 'micro sd card 128gb high endurance' (case-insensitive).

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
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: a weekly dated sample rather than live data, minute-to-minute variance of a few products, JavaScript-loaded sponsored units counted as slots only, geographic/locale scope, paid-plan requirement, 1 credit (+0.5 with history), and the derived daily cap.

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?

Content is front-loaded and nearly every clause carries information — scope, cadence, exclusions, cost. The structure is weakened by a very long run-on sentence with heavy parenthetical nesting, which makes the return-payload list harder to scan than it needs to be.

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?

With no output schema, the description carries the full burden of describing return values and does so in detail (page contents, page_summary breakdowns, change tracking, history mode). It also covers coverage caveats for the nine newer marketplaces and the cost/cap model, leaving nothing an agent needs before calling.

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 already documents keyword (case-insensitive, with example), country (11 marketplaces with per-market reading cadence), and history (weekly observations plus rank series, +0.5 credit). The description largely restates these, adding only the aggregate 'all 11 marketplaces' framing and the cost implication, so the baseline 3 applies.

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?

States a specific verb and resource — page 1 of Amazon search for a keyword as last observed — and enumerates exactly what is returned (organic order with product facts, buy box, sponsored units, Overall Pick, result count, page_summary, entrants/leavers). It explicitly distinguishes itself from serp, keywords, and product_keywords, so an agent can route correctly without opening a schema.

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?

Provides an explicit 'USE WHEN' trigger (which products/brands/sellers hold page 1, who advertises, how the page changed) and explicit exclusions with named alternatives: serp for a live page, keywords for Amazon suggestions, product_keywords for a product's ranking terms. It also states volume figures are not available and that unobserved keywords are free (keyword_not_found).

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