Skip to main content
Glama

Visibility Genies

Read saved page checks

get_saved_page_checks
Read-only

Reads the On Page SEO checks saved for this project, each ideas for one page of the project and the keyword it should rank for, from comparing it with the top 10 Google results: content (title, main heading, meta description, indexing), terms to cover (every term most top pages use that the page misses, in one row), internal links (the links to it from its own site, from Site Audit), backlinks (referring domains beside the top pages') and Core Web Vitals, each with the numbers behind it, ranked in that order of what matters for search, a missing meta description last since it does not affect ranking; then, for readers and not numbered with the ideas, since they are not Google ranking factors, its length, headings and readability beside the top pages', as facts; and the page's match with the top pages out of 100, the share of the keyword's content template terms it covers: one by its id, or a page's newest for a keyword, or else the list, newest first. Uses no credits and never buys: an On Page SEO check not saved is named with its price, which check_page_seo or the On Page SEO Checker 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_page_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkIdNoA saved check's id, from the list. Reads that check.
keywordNoThe keyword the page should rank for, such as 'espresso machine'.
pageUrlNoThe page to check, by its address, such as 'https://example.com/espresso-machines'. It must be on the project's site.
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
checkYes
boughtYes
checksYes
savedAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark it read-only and non-destructive; the description adds that it uses no credits and never buys, and that unsaved checks are named with a price. That is useful cost behavior beyond the annotations.

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

Conciseness2/5

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

The entire description is one sprawling sentence with semicolons and nested clauses, making it hard to parse. It is not front-loaded beyond the first 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 an output schema present, the description need not explain return values, yet it does so thoroughly. It also covers cost and selection, making it complete for this read-only tool.

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 the schema already documents all six parameters. The description adds selection semantics for checkId/keyword/pageUrl but little else beyond the schema.

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?

The description states a specific verb and resource ('Reads the On Page SEO checks saved for this project') and names the sibling that spends credits. The long clause about check contents muddies the opening, but the core purpose is identifiable.

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?

It explains the three selection modes (by id, newest for keyword, or list) and explicitly contrasts with check_page_seo, which pays for unsaved checks. It does not spell out when to prefer the list vs a single check beyond that.

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