Skip to main content
Glama

Visibility Genies

Save keywords

save_keywords
Destructive

Saves up to 500 keywords to a project's saved list, and can tag them. Buys no data and uses no credits. Pass metrics to keep the numbers you already researched with them.

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>",
      "keywords": "<keywords>"
    },
    "name": "save_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags to put on the keywords.
metricsNoVolume, difficulty and CPC to store with the keywords, for example copied from research_keywords rows, so nothing is bought again.
tagModeNoWithout it, keywords already saved are skipped and keep their tags, and only new ones get the tags. 'append' adds the tags to every keyword listed, and 'replace' makes them its only tags (tags required).
keywordsYes1-500 keywords to save.
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
tagsYes
tagModeYes
keywordsYes
projectIdYes
savedCountYes
languageCodeYes
locationCodeYes
skippedCountYes

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 flag this as a non-read-only, destructive operation, and the description usefully adds that no credits are spent and no data is purchased — cost behavior the annotations do not convey. It does not mention the tag-overwrite risk that the destructiveHint implies ('replace' makes tags exclusive), but it also does not contradict that hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, no filler. The primary action and its limit come first, followed by the cost fact and the metrics rationale, so an agent gets the essentials in the opening clause.

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 seven parameters, a full input schema, an output schema, and destructive/read-only annotations, the description need not restate field mechanics. It covers purpose, cost, and the metrics use case, leaving only tagMode's overwrite consequence unmentioned at the prose level, where the schema already documents it in detail.

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 schema carries the parameter mechanics and a baseline 3 would be defensible. The description still adds real meaning by explaining what the metrics array is for — preserving already-researched numbers so nothing is bought twice — which links the parameter to the neighboring research tools.

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 states a specific verb and resource ('Saves ... keywords to a project's saved list') plus a hard capacity limit (500) and the optional tagging behavior. This is enough to distinguish it from read-side siblings like list_saved_keywords or research_keywords 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?

'Buys no data and uses no credits' clearly frames this as the persistence step for work you already paid for, and 'Pass metrics to keep the numbers you already researched with them' tells the agent the intended workflow with research_keywords. It stops short of naming alternatives or stating when not to save, so it reads as clear context rather than a full decision rule.

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