Skip to main content
Glama

Visibility Genies

Read a content template

get_saved_content_template
Read-only

Reads a keyword's content template, from its top 10 Google results: the typical length of the pages (the middle half of their word counts, a fact and not a target: Google sets no word count), the median number of subheadings and the median readability (0 hard to 100 easy), which help readers and are not Google ranking factors, the terms most of the pages use, each in all its forms, with how many use each, and each page with its headings, or why it could not be read. Length and terms are compared only when at least 5 pages could be read, as saved for this project, or lists every saved template when no keyword is given. Uses no credits and never buys: a template not saved is named with its price, which build_content_template or the Content Template 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>"
    },
    "name": "get_saved_content_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordNoThe keyword whose template to read. Omit to list every saved template.
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
templateYes
templatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavior beyond them: zero credit consumption, that an unsaved template is only named with a price, the 5-readable-page minimum before length and terms are compared, and per-page failure reasons. That is genuine operational context an agent needs before calling.

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?

The verb and resource are front-loaded, so the intent lands in the first clause. However, the body is a long run-on chain of parenthetical asides ("a fact and not a target: Google sets no word count") that costs the reader more than it returns, and the return-shape inventory could be trimmed given an output schema exists.

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 and annotations, this covers scoping, cost, and the sample-size threshold that governs whether comparisons appear. What remains unstated, chiefly the effect of languageCode/locationCode on the fetched results, is already handled by the schema.

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%, so all four parameters already carry their own documentation, establishing a baseline of 3. The description reinforces that omitting keyword falls back to listing every saved template and that results are scoped "as saved for this project," but adds nothing about languageCode or locationCode beyond 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 a keyword's content template") and immediately scopes the source ("from its top 10 Google results"), then enumerates what the template contains. An agent can distinguish it from build_content_template without opening the schema.

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?

Explicitly states the alternate mode ("lists every saved template when no keyword is given") and routes the unsaved case to the sibling that pays ("which build_content_template or the Content Template page pays"). It also declares the cost posture upfront ("Uses no credits and never buys"), so the agent knows when to prefer this read over the build tool.

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