KDP Niche Research

list_niches

List available KDP niche keywords ordered by demand score.

Use this to discover what Kindle publishing niches are available for
detailed research. Returns keywords ordered by demand score (highest first).

This endpoint is free — no payment required.

Args:
    limit: Number of results to return (1-100, default 20)
    offset: Pagination offset (default 0)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedMay 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses ordering (highest first), the free nature, and pagination parameters, which gives the agent confidence that this is a safe read operation. However, it doesn't discuss potential rate limits or data freshness, so it's not fully transparent.

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

Conciseness5/5

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

Well-structured with a clear summary sentence, usage hint, free note, and an Args list. Each part serves a purpose and is front-loaded.

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 a simple list tool with an output schema, the description covers the core purpose, usage context, parameters, and an additional note about pricing. It is complete enough for an agent to invoke correctly.

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

Parameters5/5

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

Schema has no descriptions for parameters, and the description compensates by fully explaining limit (including range and default) and offset (default). This exceeds what the schema provides.

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?

Clearly states the tool lists available KDP niche keywords ordered by demand score. The mention of 'available for detailed research' distinguishes it from the sibling research_niche tool by framing it as a discovery step.

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

Usage Guidelines4/5

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

Provides clear context on when to use it ('to discover what Kindle publishing niches are available'), but doesn't explicitly name the alternative research_niche or state when not to use. This limits it to a 4 rather than a 5.

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

All KDP Niche Research tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

The two tools are completely distinct: list_niches provides an overview of available keywords, while research_niche dives into detailed metrics for a specific keyword. There is no overlap in purpose or output, making selection unambiguous.

Naming Consistency5/5

Both tools follow a consistent verb_noun convention with lowercase and underscores: list_niches and research_niche. The pattern is predictable and matches the server's research-focused domain.

Tool Count3/5

With only two tools, the server feels thin for a complete research workflow, though it covers the essential 'discover then investigate' flow. The count is borderline but not entirely inadequate given the focused purpose.

Completeness4/5

The core workflow of listing niches and researching a specific niche is covered with no dead ends. Minor gaps include lack of bulk research or filtering options, but agents can manually iterate over list results to achieve similar outcomes.

Resources

Need Help?