Skip to main content
Glama

Get Master Keyword List for a Niche

get_niche_keywords
Read-only

Retrieve a niche's master keyword list with search volume, relevancy scores, competitor ASIN organic ranks, suggested bids, and origin so you can analyze ranking and performance metrics.

Instructions

Use this when the user asks about keywords, search terms, or search volume for a niche. Retrieves the master keyword list for the specified Niche — the relevant search terms monitored for ranking and performance metrics. For each keyword, returns search volume, relevancy (numeric score or "Outlier"), and competitor ASIN organic ranks (asinRanks: { ASIN -> rank | null }), the exact-match suggestedBid (min / max / median in cents; null when not yet fetched for the latest dive), plus origin: mkl (found by the dive), manual (added by hand with add_niche_keywords), outlier / residue (moved in from those lists). Only manual, outlier and residue keywords can be taken out with remove_niche_keywords. Keywords hidden by the niche's keyword exclusions are not listed; see list_keyword_exclusions. Also returns the latestResearchDate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nicheId": "<nicheId>"
    },
    "name": "get_niche_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheIdYesThe unique identifier of the Niche (from `list_niches`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description adds substantial behavioral context beyond that: the meaning of origin values, which origins can be removed via remove_niche_keywords, the interaction with keyword exclusions, and the presence of latestResearchDate. It fully characterizes what the tool returns without contradicting the read-only annotation.

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?

The description is front-loaded with the usage trigger and then packs return-field semantics, origin meanings, and exclusion behavior into one dense but purposeful paragraph. Given the absence of an output schema, every clause carries useful information.

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?

Although there is no output schema, the description explains all important return fields, origin semantics, removal restrictions, and exclusion behavior. For a one-parameter read tool, nothing essential needed for correct invocation or interpretation is missing.

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 sole nicheId parameter is already documented in the schema as coming from list_niches. The description reinforces that the list is for the specified Niche but does not add meaningful syntax or format details beyond the schema.

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 ('Retrieves the master keyword list') and scopes it to a specified Niche, then enumerates the returned metrics and keyword origins. This lets an agent distinguish it from sibling tools like get_niche_outlier_keywords and list_keyword_exclusions.

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 an explicit trigger: 'Use this when the user asks about keywords, search terms, or search volume for a niche.' It also notes that exclusions-hidden keywords are omitted and directs the agent to list_keyword_exclusions, but it does not explicitly compare this tool against sibling keyword-list tools.

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