Skip to main content
Glama

Visibility Genies

Read saved topic research

get_saved_topic_research
Read-only

Reads a Topic Research already bought for this project: 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. Uses no credits and never buys: a topic not saved is named with its price, which research_topic or the Topic Research page pays.

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": "get_saved_topic_research"
  }
}

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.

Output Schema

NameRequiredDescriptionDefault
metaNo
boughtYes
savedAtYes
researchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish a safe, non-destructive, read-only operation, and the description adds behavior those annotations cannot express: it consumes no credits, it never triggers a purchase, and an unsaved topic yields a name-plus-price result instead of an error or a charge. What it does not disclose is pagination or the size/shape limits of the returned payload, but the output schema covers the response shape.

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 verb and resource, and the cost/no-purchase guarantee is placed prominently in the second sentence. The first sentence is a long run-on enumeration of return fields that partly duplicates the output schema, which costs a little efficiency but keeps the important scoping upfront.

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 read tool with full annotation coverage, complete parameter descriptions and an output schema, nothing an agent needs in order to call it correctly is missing; the no-credit guarantee and the unsaved-topic outcome close the only behavioral gaps.

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 itself documents every parameter including the language and location fallbacks to the project's default market. The description only refers in passing to "this project" and "a topic" and adds no syntax or format guidance for languageCode or locationCode, so the schema does the heavy lifting and the baseline of 3 applies.

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 ("Reads a Topic Research already bought for this project") and then enumerates exactly what comes back — up to 300 keywords grouped into subtopics with volume, difficulty, questions and headlines. The boundary with the purchasing tool is explicit, so an agent can tell this apart from research_topic or the other read/list siblings immediately.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use-this and when-to-use-the-alternative: use this for research that is already saved, and if the topic is not saved the call returns the topic with its price, which research_topic or the Topic Research page pays. That is a direct routing rule rather than implied usage.

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