Skip to main content
Glama

Visibility Genies

Read saved questions

get_saved_questions
Read-only

Reads Questions already bought for this project: up to 200 questions people search about a topic (found by question words in the market's language: English, German, French, Spanish, Italian, Dutch and Portuguese have their own, and other languages use the English ones), most searched first, each with Google search volume, difficulty, AI search volume, and the People Also Ask question on the topic's saved SERP analysis it rewords (about 70% of its words shared), with each People Also Ask question listed. Uses no credits and never buys: questions or AI search volume not saved are named with their price, which find_questions or the Questions 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_questions"
  }
}

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
questionsYes
aiSearchVolumeErrorYes

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?

Goes well beyond the readOnly/destructive annotations: it discloses the credit cost (none), the 200-item ceiling, the sort order, the language fallback rule (English/German/French/Spanish/Italian/Dutch/Portuguese have their own question words; others fall back to English), and the ~70% word-overlap heuristic by which People Also Ask questions are matched to the saved SERP analysis. These are exactly the behavioral details an agent cannot infer from structured fields.

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?

The verb and resource are front-loaded, but the body is one overstuffed sentence with two deep parentheticals, making it hard to parse on a first read. Every fact is relevant, yet the nesting of language lists and the 70% overlap clause could be split into shorter sentences without losing content.

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?

For a read tool with a full output schema, no return-value explanation is needed, and the description still covers cost, result cap, ordering and language behavior. The only gap is pagination/truncation semantics at the 200-question limit, which an agent might need to know when results are cut off.

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 baseline would be 3, but the description adds real meaning on top: it explains how the language dimension actually behaves (per-language question vocabularies with English fallback) and ties topic to market language. It does not elaborate on locationCode, whose market-specific data caveats are already documented 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?

Opens with a specific verb and resource ('Reads Questions already bought for this project') and immediately sets scope: up to 200 questions, ordered most searched first, each with search volume, difficulty, AI search volume and People Also Ask data. It is clearly differentiated from the buying sibling find_questions, so an agent can tell the two apart without opening a schema.

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?

States plainly that this tool 'Uses no credits and never buys', and that anything unsaved is reported with its price to be paid via find_questions or the Questions page — an implicit but clear rule for when to call this versus the buying alternative. What is missing is an explicit statement of when to prefer this tool over other saved-read siblings (e.g. get_saved_topic_research), but the buy/no-buy split is the decisive case and it is covered.

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