Skip to main content
Glama

ai_get_top_cited_pages

Retrieve the top cited pages from imported AI citation reports for a site, with an optional limit, to identify content AI assistants cite frequently.

Instructions

Get the top cited pages from imported AI citation reports.

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": {
      "siteUrl": "<siteUrl>"
    },
    "name": "ai_get_top_cited_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of pages to return (default 20)
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden, and it only implies read-only behavior through the verb 'Get'. It does not say what happens when no citation report has been imported, how 'top' is ranked, or anything about the shape of the result set.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than tightness.

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

Completeness3/5

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

For a two-parameter read tool with fully documented schema, the description covers the essential purpose. With no annotations and no output schema, however, it leaves the agent guessing about the prerequisite import step and the returned fields (pages plus citation counts, ordering).

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%, with both 'siteUrl' and 'limit' (including its default of 20) documented in the schema itself. The description adds no extra meaning such as whether siteUrl must match an imported report's URL, so baseline 3 applies.

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 and resource ('Get the top cited pages') and names the data source ('imported AI citation reports'), which distinguishes it from siblings like ai_get_top_queries or ai_get_top_intents. It stops short of explicitly routing between those siblings, but the resource is concrete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites such as needing a citation report imported first, and no comparison to the other ai_get_top_* tools. The phrase 'imported AI citation reports' faintly implies a dependency but never states it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.