Skip to main content
Glama
Sign In

Logimu

by com.logimu
OverviewDiscussionsAdmin

keywords

Read-onlyIdempotent

Amazon's OWN autocomplete suggestion lists for a seed term, from Logimu's continuous harvest (since Aug 2026, 11 marketplaces): up to 6 lists - one per crawled prefix / department - each term with its position 1-10 WITHIN that list, when it was first and last observed and the marketplaces it was observed in, plus related observed vocabulary starting with the seed. history=true adds every observation of each list since the harvest began (a term entering, leaving or moving position). compare='us,uk,de' instead returns the seed's primary list on each marketplace and a matrix of positions per marketplace. USE WHEN the user asks what buyers type for X, wants listing / backend keyword language, seeds for product research, or how a term's suggestions differ by country. NOT volume figures (Amazon publishes none for its suggestions and none are implied), NOT a product-ranking map - which products appear on page 1 for a term is keyword_rankings, the keywords a product shows up for is product_keywords. Positions are comparable only within one list. COST: paid plan required (listed only for keys on a paid plan), 1 credit per lookup or compare, +0.5 with history when at least one closed observation exists; an unknown seed is free. Counts against the derived daily cap (default 2,000 calls per account).

Input Schema

NameRequiredDescriptionDefault
seedYesA seed term or prefix, at least 3 characters, e.g. 'electric toothbrush'.
compareNoComma-separated marketplaces to compare instead of one lookup, e.g. 'us,uk,de' (2-11).
countryNoAmazon marketplace (ignored when compare is given).us
historyNoAlso return each list's observation history (+0.5 credit when a closed observation exists).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: paid-plan gating, credit cost per lookup and history surcharge, free unknown seed, and the derived daily cap. It also discloses a key analysis constraint ('positions are comparable only within one list'), which is not in any structured field.

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?

Front-loaded with the resource and output shape, and each sentence carries information (mode behavior, use cases, exclusions, pricing). It is a single dense paragraph that runs long, but no sentence is filler.

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 fully specifies the return shape for both modes, plus cost model, rate limit, and interpretation caveat. An agent has everything needed to call it correctly and to set user expectations.

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, but the description adds genuine semantics: history=true means every observation of each list (entering, leaving, moving position), and compare returns a primary list plus a position matrix per marketplace. It stops short of explaining the country-vs-compare precedence, which the schema itself covers.

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+resource ('Amazon's OWN autocomplete suggestion lists for a seed term') with the exact output shape (up to 6 lists, position 1-10, first/last observed, marketplaces, related vocabulary). Explicitly distinguishes itself from siblings by naming keyword_rankings and product_keywords as the tools for adjacent questions.

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' clause (buyer language, backend keywords, product research seeds, per-country differences) and 'NOT' exclusions (not volume figures, not a product-ranking map) with the correct alternative named for each exclusion.

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