Skip to main content
Glama

Visibility Genies

Check a page

check_page_seo

Runs an On Page SEO check: 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. Estimated price per On Page SEO check: up to $0.08, for the keyword's content template when no current one is saved, the page's text when none is saved and Visibility Genies' crawler, which reads it free first, cannot read it, and the referring domains of the page and the top pages with none saved in the last 24 hours. Title and indexing come from what Site Audit saved, and Core Web Vitals from real Chrome users (the free Chrome UX Report) when the workspace has a key and the site enough visits, else Site Audit's lab Lighthouse test; none is bought. An On Page SEO check whose data is all current is answered from what is saved at no charge, and every one opens free on the On Page SEO Checker page. With readPageAgain, it reads only the page's text again, free by Visibility Genies' crawler first and bought only when it cannot, for up to $0.01, and saves a new check from it. 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>",
      "pageUrl": "<pageUrl>",
      "keyword": "<keyword>"
    },
    "name": "check_page_seo"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesThe keyword the page should rank for, such as 'espresso machine'.
pageUrlYesThe 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.
readPageAgainNoReads the page's text again even though a saved copy is current, as when the page changed since its last check: free by Visibility Genies' crawler first, and bought only when the crawler cannot read it. Saves a new check from it with what else is saved; nothing else is bought. Needs a saved check of the page for the keyword in this market.
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
checkYes
boughtYes
checksYes
savedAtYes
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations mark this non-read-only and open-world, and the description goes well beyond them: it names the price ceiling (up to $0.08, up to $0.01 for readPageAgain), the $2.00 workspace spend limit, the refusal-then-retry-with-approvedMaxCostUsd flow, and which data is free (cached checks, the crawler's free read) versus bought. It also discloses data provenance (Site Audit for title/indexing, Chrome UX Report versus lab Lighthouse for Core Web Vitals). What it does not describe is the failure mode when the page is off the project's site or the keyword yields no template, but the disclosure is otherwise unusually rich for a billable tool.

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 verb is front-loaded, but the body is a roughly 330-word run-on of semicolon-chained clauses ('...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...') that is genuinely hard to parse. readPageAgain's cost is stated twice, and much of the output enumeration duplicates what the output schema already carries.

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 billable, open-world, mutation-adjacent tool, the definition covers what an agent actually needs: cost estimate and ceiling, the spend-limit refusal and approval path, free cached answers, data provenance, and the readPageAgain contract. An output schema is present, so the heavy return-value prose is redundant rather than a completeness gap.

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, and the description still earns an upgrade: it explains the operational consequences of readPageAgain (requires an existing saved check for that page and keyword in that market, saves a new check, buys nothing else) and the recovery workflow for approvedMaxCostUsd after a spend-limit refusal. Those are behavioral contracts the parameter descriptions only partly convey.

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 opening clause gives a specific verb and resource: 'Runs an On Page SEO check: ideas for one page of the project and the keyword it should rank for, from comparing it with the top 10 Google results.' The scope is further pinned down by enumerating what the check returns (content, terms, internal links, backlinks, Core Web Vitals) and by the 0-100 match score, so an agent can tell this apart from retrieval or analytics siblings 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the description notes that a check whose data is current is 'answered from what is saved at no charge,' which hints at a cheaper retrieval path, but it never names that alternative or tells the agent when to prefer it. The only genuine when-to-use guidance is scoped to a parameter ('with readPageAgain ... as when the page changed since its last check'), leaving the core decision to run a fresh check unaddressed.

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