Skip to main content
Glama

Visibility Genies

Find top searches

find_top_searches

The most searched keywords in a market, highest monthly volume first, narrowed by text they contain, a least volume and a highest keyword difficulty, each with its volume, CPC, difficulty and search intent. Estimated price: up to $0.05, one market data request for up to 100 keywords, billed by the rows returned. The same filters and market saved within a day are read free, and they open free on the Top searches page. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>"
    },
    "name": "find_top_searches"
  }
}

Input Schema

NameRequiredDescriptionDefault
containsNoText every keyword must contain, e.g. 'shoes'.
minVolumeNoThe least monthly search volume a keyword may have.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
locationCodeNoMarket location code, for example 2840 for the United States. When left out, the project's default market is used (shown by list_projects and changed in project settings). A few countries, Iceland (2352) among them, only have Google Ads data: search volume, CPC and trends are available there, but keyword difficulty, search intent and domain analytics are not.
maxDifficultyNoThe highest keyword difficulty (0 to 100) a keyword may have.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
boughtNo
keywordsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare openWorldHint and readOnlyHint=false; the description carries the real behavioral burden: an estimate up to $0.05, per-row billing, a 100-keyword cap, free re-reads of the same filters and market within a day, and the workspace agent spend limit of $2.00 that can block a call mid-flow. That pre-purchase reservation and refusal behavior is exactly what an agent needs before calling a billable tool.

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 result shape and filtering come first, then price, then the spend-limit refusal path, which is a sensible front-loading for an agent that must decide before spending. It is dense with billing detail and slightly long, but each sentence carries operational 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?

For a billable, open-world search tool with a full output schema, everything an agent needs is present: cost ceiling, what triggers a refusal, how to recover, and how caching affects repeat calls. Return values need not be described because an output schema exists.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: the filters are collectively free to re-run within a day, and approvedMaxCostUsd is only set after a refusal and only with user consent. The remaining parameters (contains, minVolume, maxDifficulty) are already fully explained by 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?

The description names the exact resource (the most searched keywords in a market), the ordering ('highest monthly volume first'), the filters that narrow it, and the fields returned with each row (volume, CPC, difficulty, search intent). That level of specificity separates it from sibling query tools such as find_questions or find_ad_advertisers without needing to name them.

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?

It gives a clear usage context through the cost and spend-limit rules, including the exact recovery procedure when a call is refused (ask the user, then retry with approvedMaxCostUsd). It does not state when to prefer a different search tool, so it stops short of full alternative routing.

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.

Resources