Skip to main content
Glama

Visibility Genies

Read a keyword strategy

get_saved_keyword_strategy
Read-only

Reads a keyword strategy saved on the Keyword Strategy page: the project's keywords grouped into topics, each with its primary keyword, secondary keywords, total volume, average difficulty, intent, the page that should target it and its warnings (mixed search intents, a page two topics share, keywords whose saved SERP analyses put them on one page or apart), plus the keywords in no topic, with navigational searches apart. Also lists every saved strategy. Uses no credits and calls no provider. No agent tool builds a strategy: the grouping runs on the page, which prices it first.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
strategyIdNoThe saved strategy to read, from this tool's list. Omit to read the newest.

Output Schema

NameRequiredDescriptionDefault
metaNo
topicsYes
strategyYes
ungroupedYes
strategiesYes
navigationalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety profile is covered. The description adds genuinely new behavioral context: 'Uses no credits and calls no provider' tells the agent this is a free, local read, which is decision-relevant when budgeting calls. It also discloses the shape of the warnings payload, though describing return contents is partly redundant with the existing output schema.

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?

Purpose is front-loaded, but the middle is a dense, comma-chained enumeration of return fields that belongs in the output schema rather than the description. Some wording is redundant ('Uses no credits and calls no provider') and the closing note about page-side grouping pricing is vague and only loosely connected to invoking the tool.

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 100% schema coverage, a full output schema, and safety annotations, the description supplies the remaining needed context: cost, provider behavior, and that no strategy-building tool exists. It is complete enough to call correctly, with the only real surplus being the field-by-field return enumeration.

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 both parameters are already fully documented, including the 'from this tool's list' sourcing of strategyId. The description adds only marginal meaning, confirming that the call also lists every saved strategy, which hints at strategyId discovery but never explains parameter behavior beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 keyword strategy saved on the Keyword Strategy page') and enumerates the payload in enough detail that an agent knows it is distinct from list_saved_results or read_saved_result. It does not explicitly name a sibling it replaces, so sibling differentiation is only implied by the resource description.

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?

Clear context for when this applies: reading a saved keyword strategy by project, omitting strategyId for the newest, and listing all saved strategies for discovery. It also pre-empts a dead end by stating 'No agent tool builds a strategy', steering the agent away from searching for a create/build sibling. No explicit 'use X instead when...' routing is present.

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