Skip to main content
Glama

Vip Niches Tool

vip_niches
Read-only

VIP niches, a feature of the Pro plan: the best niches to build an app in, ranked in the order to take them, from the public niche catalog and the account's own researches. The order follows the rule-based verdict: "go" before "maybe" ("no" never enters), then the sum of the verdict factors, then a phrase with weak search results to enter by, signs of room, confidence and monthly demand. Each item: rank, phrase, country, language, verdict, confidence, score, demand, entry {phrase, demand}, openings (signs of room found), trend, stores and search readings, platform, cac_usd and ltv_usd when the report has them (napkin estimates: only the click price is measured, conversion is the share of paid clicks in percent the model assumed, the price and months are assumed too), first_step (the first validation step of the report), url (the research page, or the catalog page for a niche of the catalog) and research_id (for get_report; null for catalog niches, whose report is read on the catalog page). Web-only services are left out unless web is true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vip_niches"
  }
}

Input Schema

NameRequiredDescriptionDefault
webNotrue to include niches the report advises to build only as a web service.
limitNoHow many niches to return, 1-30 (default 30).
countryNoISO code of one country, such as US or BR; all countries when absent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, so the description carries real weight and does: it discloses the ranking rule ("go" before "maybe", "no" never enters), that catalog and research niches are merged, that cac_usd/ltv_usd are napkin estimates with only click price measured and conversion/price/months assumed, and that catalog niches have research_id null. That is substantive non-obvious context. It stops short of stating plan-gating failure behavior for non-Pro accounts.

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

Conciseness3/5

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

Content is largely relevant because no output schema exists, but it is delivered as one ~180-word run-on sentence with semicolon-chained field lists. The purpose is stated first, which helps, yet the field inventory crowds out any usage framing and would read far better as a short purpose sentence plus a structured field note.

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?

With no output schema, the item-by-item field breakdown is genuinely necessary and covers returns, ordering semantics, provenance, and estimate caveats, so an agent knows what it will get. Remaining gaps are minor: no mention of pagination beyond `limit`, empty-result behavior, or what happens on a non-Pro account.

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 coverage is 100%, so the schema already documents all three parameters. The description reinforces `web` by restating the exclusion rule it controls, but adds nothing on `limit` or `country` beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: the best niches to build an app in, ranked in the order to take them, drawn from the public niche catalog plus the account's own researches, as a Pro-plan feature. It does not distinguish itself from siblings such as find_growth_niches or get_research, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is only implied. The one actionable routing hint is that `research_id` feeds get_report, and that web-only niches are dropped unless `web` is true. There is no explicit statement of when to pick this over find_growth_niches or how to drill from here into a report.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.