Skip to main content
Glama

Visibility Genies

Build a content template

build_content_template

Builds 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. Estimated price per keyword: up to $0.02, for the SERP analysis, when none of the last 12 hours is saved, then each page with no saved copy. A template whose results are still current is answered from what is saved at no charge, and every build opens free on the Content Template page. Pages that could not be bought are listed, and the next call buys only them. When Google hid the address of every top result on desktop, the mobile results are bought once more, charged on top of that estimate but never above the call's maximum, and the template says it came from mobile. When Google hid the address of some results, the template is built from the others (at least 3 must be readable) and names the ones it could not read; with fewer, no template is built and the answer says what the search results were charged. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": "build_content_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
mobileNoBuild from Google's mobile results instead of the desktop ones. Use it only after a build said too few top results could be read on desktop and that mobile was not tried: it is priced and held as a new build.
keywordYesThe keyword a page should rank for, such as 'espresso machine'.
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.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
boughtYes
savedAtYes
templateYes
templatesYes
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true, yet the description discloses the charging model (up to $0.02 per keyword, cached results free), the workspace spend limit with hold and margin semantics, the refusal path and required approvedMaxCostUsd retry, and mobile fallback billing. Failure modes are spelled out concretely, including the 3-readable-page minimum and the no-template outcome with search charges.

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?

Long but dense with distinct facts; each sentence carries new information about pricing, fallbacks, or refusal handling. The structure is less disciplined than it could be - cost rules, readability caveats, and failure paths are interleaved in one sprawling block rather than grouped, and filler like 'a fact and not a target' and 'which help readers and are not Google ranking factors' could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, open-world tool with six parameters and an output schema, the description covers everything an agent needs before calling: cost estimate, spend limits, approval escalation, mobile fallback conditions, minimum readable results, and what is returned when nothing can be built. Return value details are correctly left to the output schema.

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 baseline is 3; the description still adds meaning by explaining how the cost cap interacts with parameters ('never above the call's maximum', 'a call whose maximum is above the limit is refused') and by tying approvedMaxCostUsd to the ask-the-user-then-retry flow. This goes past restating schema text and clarifies runtime semantics of the cost parameters.

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 ('Builds a keyword's content template') and immediately scopes the input ('from its top 10 Google results'). It also enumerates what the template contains, so an agent knows precisely what it gets back and how it differs from a read-only retrieval of a saved template.

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?

Gives rich conditional guidance: a still-current template is answered from the saved copy at no charge, unbought pages are listed so the next call buys only them, mobile should only be retried after a desktop build reported too few readable results, and cost above the spend limit must be user-approved before retrying. It never names the sibling read tool (get_saved_content_template) as an explicit alternative, so the routing guidance is implied rather than stated.

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