Skip to main content
Glama
Data-Dive-Tools

DataDive MCP

Official
by Data-Dive-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List DataDive Niches

list_niches
Read-only

Retrieve tracked market niches with pagination. Filter by label or competitor ASIN to find the niche ID for keyword and competitor research.

Instructions

Use this first when the user asks about their niches, or to find a nicheId for use with get_niche_keywords, get_niche_competitors, or get_ranking_juice. Retrieves a paginated list of Niches, newest dive first. Each Niche represents a market segment or product category being tracked. Returns nicheId, heroKeyword, nicheLabel, marketplace (com/uk/de/...), and latestResearchDate per niche, plus pagination metadata (currentPage, pageSize, total, lastPage, hasNext, hasPrev). Narrow with searchText (label/keyword) or searchAsin (a competitor ASIN) instead of scanning pages; a page holds at most 50 niches, so the full list of a large account needs several calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderByNoSort field: `lastDived` (by latestResearchDate, newest first by default) or `name` (by nicheLabel, A→Z by default). Defaults to `lastDived`.
pageSizeNoItems per page (max 50). Defaults to 20.
sortOrderNoSort direction. Defaults to DESC for `lastDived` and ASC for `name`.
searchAsinNoOnly niches whose competitor set contains this ASIN (10 characters, e.g. B08N5WRWNW).
searchTextNoCase-insensitive partial match on the niche label or hero keyword. Prefer this over paging through everything when the user names a niche.
currentPageNoPage number, 1-indexed. Defaults to 1. Keep requesting the next page while `hasNext` is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.12.0
    • changedInput schema / properties / currentPage / description
      Previous value: -"Page number, 1-indexed. Defaults to 1."New value: +"Page number, 1-indexed. Defaults to 1. Keep requesting the next page while `hasNext` is true."
    • addedInput schema / properties / orderBy
      Added value: +{
+  "description": "Sort field: `lastDived` (by latestResearchDate, newest first by default) or `name` (by nicheLabel, A→Z by default). Defaults to `lastDived`.",
+  "enum": [
+    "lastDived",
+    "name"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / searchAsin
      Added value: +{
+  "description": "Only niches whose competitor set contains this ASIN (10 characters, e.g. B08N5WRWNW).",
+  "pattern": "^[A-Za-z0-9]{10}$",
+  "type": "string"
+}
    • addedInput schema / properties / searchText
      Added value: +{
+  "description": "Case-insensitive partial match on the niche label or hero keyword. Prefer this over paging through everything when the user names a niche.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / sortOrder
      Added value: +{
+  "description": "Sort direction. Defaults to DESC for `lastDived` and ASC for `name`.",
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.11.0
    • changedInput schema / properties / pageSize / description
      Previous value: -"Items per page (max 100). Defaults to 20."New value: +"Items per page (max 50). Defaults to 20."
    • changedInput schema / properties / pageSize / maximum
      Previous value: -100New value: +50
  3. First observedv0.8.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, which the description aligns with by describing a retrieval operation. It adds useful behavioral context: pagination metadata (currentPage, pageSize, hasNext), sort order by newest first, and the 50-item page limit, which are not in the annotations.

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?

The description is a single paragraph but logically organized: use case first, then return values, then optimization tips. Every sentence adds information, but it is slightly dense; a bulleted structure could improve skimmability without adding length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with a rich schema and no output schema, the description covers when to use it, what it returns, how to paginate, and how to narrow results. It lacks explicit mention of default values for pageSize/orderBy, but these are fully documented in the schema, so the description is sufficiently complete.

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?

The input schema already has 100% parameter description coverage, including defaults and examples. The description only reiterates the page size limit and search use cases without adding new meaning, so it meets the baseline but does not elevate it.

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?

The description uses specific verbs ('list', 'retrieves') with a clear resource ('Niches') and immediately states its primary use case: finding a nicheId for other tools like get_niche_keywords. It also defines what a Niche is, distinguishing this listing tool from sibling tools that operate on a specific niche.

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?

The description explicitly states when to use the tool ('Use this first when the user asks about their niches') and gives concrete guidance on narrowing results via searchText or searchAsin instead of paging. It does not explicitly state when not to use it or name alternative tools for other scenarios, but the context is strong.

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

Deploy Server

Other Tools