Skip to main content
Glama

Visibility Genies

Read a page's view

get_page_view
Read-only

Pages: everything the project holds about one page of its own site, in one answer, to say how a page is doing. Returns the page facts (type, key page role, status code, indexable, words, last crawled, canonical), every tracked keyword whose latest check ranks this page with location, device, position and change since the check before, the tracked prompts whose AI answers cite it with engines, answers, whether the answer names the brand, last cited date and up to ten cited sentences, the open issues of the latest site audit on the page (muted and site level ones left out), and Search Console clicks, impressions, CTR (0-1 in the structured result) and position for the last 28 days against the 28 before with the top ten searches, plus Analytics organic sessions. Each part says when it has no data or is not connected. Read only and free.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA page of the project's own site, full URL or host and path. A leading www., a trailing slash and the query string are ignored.
periodNoThe period AI citations are counted over (default last_30_days). Search is always the last 28 days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
pageNo
reasonNo

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?

Goes well beyond the annotations: it discloses exclusions (muted and site-level audit issues left out), truncation limits (up to ten cited sentences, top ten searches), the comparison window (last 28 days against the 28 before), a unit caveat (CTR is 0-1 in the structured result), and graceful degradation ("Each part says when it has no data or is not connected"). The closing "Read only and free" merely restates readOnlyHint and is redundant, but the rest is substantive behavioral context.

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?

Front-loads the promise ("everything the project holds about one page") but then unloads a single sprawling run-on sentence with nested lists, making it hard to scan. Almost nothing is filler factually, yet the density and lack of sub-structure cost comprehension. A short bulleted breakdown would have delivered the same content far better.

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?

Covers the full breadth of the response for a multi-source aggregation tool, including which sections are omitted and how empty sections behave, which is important for an agent that must not misread a missing source as zero. Given an output schema exists, and safety is already carried by annotations, what remains missing is mainly sibling disambiguation, not behavioral detail.

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 url normalization, the period enum, and projectId billing already carry full documentation in the schema. The description restates that Search is always the last 28 days while period governs AI citations, which mirrors what the schema already says rather than adding new meaning. Baseline 3 applies when the schema does the heavy lifting.

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+resource ("everything the project holds about one page of its own site, in one answer") and enumerates the payload: page facts, ranked keywords, AI-cited prompts, audit issues, Search Console and Analytics metrics. An agent knows exactly what it gets. It never names a sibling such as get_landing_page_insights or check_page_seo, so overlap with those tools must be inferred from content alone.

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?

The framing "to say how a page is doing" implies a diagnostic use case, and "A page of the project's own site" bounds the input domain. But there is no explicit when-to-use or when-not-to-use statement and no routing to alternatives, even though sibling tools like get_landing_page_insights and check_page_seo sound like near-overlapping entry points. The single multi-source aggregate nature implies the tool is for a broad snapshot rather than a single metric, but the agent must infer 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