get_v1_keyword_generator_amazonFind what people are searching for on Amazon, and align your product listings with those terms. Group: Keyword Research. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | ||
| keyword | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions billing (1 Credit) and grouping but does not describe output format, data source behavior, limitations, or required inputs. This is a significant gap for a tool with no output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three short sentences, front-loaded with the core purpose and followed by compact metadata. There is no filler or redundant wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description should clarify return values and parameter behavior, but it does not. The tool is simple, so the description is partially adequate, but it omits important operational context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain the 'country' or 'keyword' parameters beyond what their names and schema examples already convey. It fails to compensate for the lack of schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Find') and resource ('what people are searching for on Amazon'), clearly identifying the tool's function. The explicit mention of Amazon distinguishes it from sibling keyword generators for Bing, Google, and YouTube.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'align your product listings with those terms' implies an Amazon listing optimization use case, but there is no explicit guidance on when to prefer this tool over alternatives or when not to use it. No exclusions or sibling comparisons are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct SEO function: backlinks, broken links, keyword difficulty, keyword generation per platform, rank checking, SERP analysis, and website metrics. The platform-specific keyword generators (Amazon, Bing, Google, YouTube) are clearly differentiated. No two tools overlap in purpose.
All tools follow a uniform 'get_v1_' prefix followed by a descriptive noun phrase, creating a predictable and coherent pattern. The consistent use of snake_case and the same verb prefix makes the toolset easy to scan and understand.
With 11 tools, the set is well-scoped for an SEO data provider. Each tool represents a meaningful API endpoint without unnecessary duplication or bloat. The count falls comfortably within the ideal range for a focused server.
The toolset covers core SEO workflows: link analysis (backlinks, broken links, authority), keyword research (difficulty, generators, rank), and SERP/traffic metrics. Minor gaps exist, such as missing site audit or content explorer tools, but the provided surface handles typical use cases effectively.