Skip to main content
Glama

Visibility Genies

Research a topic

research_topic

Buys Topic Research: up to 300 keywords related to a topic, grouped into subtopics (by Google's product and service categories, or by the words they share), each with its keywords, total search volume, average difficulty, the questions among them, and the headlines that rank for its top keyword where a SERP analysis is saved. Estimated price up to $0.10 per topic. A topic researched in the last 24 hours is answered from its saved copy at no charge, and every purchase opens free on the Topic Research page. Headlines are only read, never bought. 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>",
      "topic": "<topic>"
    },
    "name": "research_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe topic, such as a product, service or subject: 'coffee', 'running shoes'.
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.
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
boughtYes
savedAtYes
researchYes
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say it is not read-only and is open-world; the description goes much further, disclosing per-topic price (up to $0.10), the free 24-hour cache path, the workspace agent spend limit ($2.00 default), that funds held during a run are estimate-plus-margin and settled at actual cost, and that over-limit calls are refused before any purchase with the estimate and maximum returned.

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?

Front-loaded with the deliverable and price, then the spend/approval mechanics, so the most decision-relevant information comes first. It is a dense single block of long clauses with no breaks, which makes it harder to scan than it needs to be.

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 paid, open-world tool with five parameters, the description covers cost, caching, spend limits, refusal behavior and escalation. With annotations and a full output schema also present, an agent has everything needed to call this correctly or correctly decline to.

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% and the schema already explains topic, projectId, languageCode, locationCode and the approvedMaxCostUsd approval rule, so the baseline applies. The description reinforces when approvedMaxCostUsd is set (after a refusal, with user approval) but adds little parameter meaning not already in 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 ('Buys Topic Research') and immediately defines the deliverable: up to 300 keywords grouped into subtopics by Google category or shared words, with volume, difficulty, questions and headlines. An agent knows exactly what comes back and that this is a paid purchase rather than a lookup.

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?

Gives clear operating context: a topic researched within 24 hours is answered free from the saved copy, headlines are read-only and never bought, and a refused call must be escalated to the user before retrying with approvedMaxCostUsd. It does not explicitly point to sibling alternatives such as research_keywords or get_saved_topic_research, so differentiation is left implicit.

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