Skip to main content
Glama

Visibility Genies

Read saved autocomplete ideas

get_saved_keyword_autocomplete
Read-only

Reads Google Autocomplete suggestions already bought for a keyword in this project, however old, for free. It never buys: a keyword not saved is named with the price get_keyword_autocomplete would pay.

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>",
      "keyword": "<keyword>"
    },
    "name": "get_saved_keyword_autocomplete"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesThe keyword typed into Google, e.g. 'ski boots'.
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
keywordYes
savedAtYes
suggestionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the description isn't carrying the safety burden. It still adds genuinely useful behavior: reads are free, results are returned regardless of age ('however old'), no purchase is ever made, and an unsaved keyword yields the price get_keyword_autocomplete would charge instead of an error.

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?

Two sentences, no filler, with the free/read-only framing front-loaded. The second sentence is slightly convoluted ('a keyword not saved is named with the price get_keyword_autocomplete would pay') but it earns its place by covering the miss case.

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 an output schema present, return values need not be explained, and annotations cover the safety profile; the description closes the main functional gap by describing the not-saved outcome. Only minor room remains, such as how market/language defaults influence which saved suggestions are returned.

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 all four parameters are documented in the schema, including the project default fallbacks for languageCode and locationCode. The description only restates that the keyword belongs to 'this project'; it adds nothing about language/market scoping or how those optional parameters affect results, so the baseline 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 Google Autocomplete suggestions already bought for a keyword') plus scope ('in this project, however old, for free'), and implicitly contrasts with the buying sibling get_keyword_autocomplete. An agent can distinguish this cached-read tool from the purchase tool without opening either 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?

Makes the selection rule clear: use this for already-purchased suggestions because it costs nothing, and it will never trigger a purchase. It names get_keyword_autocomplete as the path for a keyword that isn't saved, but stops short of an explicit 'use get_keyword_autocomplete when you want to buy' instruction, leaving one small inference.

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