Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

AI Overview eligibility

ayrank_ai_overview_eligibility
Read-only

Check whether a URL meets Google's stated conditions to be a supporting link in AI Overviews; returns eligible, not eligible, or can't check with evidence per condition.

Instructions

Use to check one URL against Google's stated conditions for being a supporting link in AI Overviews and AI Mode: robots.txt, status, noindex, unavailable_after, nosnippet and max-snippet, data-nosnippet share and canonical. Returns eligible, not-eligible or cant-check with evidence per check. Eligible never means included, and it cannot tell whether the page is indexed (only Search Console can). It does not check whether Google shows the page in an AI answer. Free AY Rank API, no key. JavaScript is not run, so content added by scripts is not seen.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe page to check, like https://example.com/page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial beyond them — the three-state outcome (eligible/not-eligible/cant-check) with per-check evidence, the explicit semantic caveat that eligible is not inclusion, that JavaScript is not executed so script-injected content is invisible, and that the API is free and needs no key. These are exactly the failure modes an agent would otherwise misreport.

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?

Front-loaded with the purpose, then the checks, then the caveats — no filler sentences, and each disclaimer prevents a real misinterpretation. It is a dense run-on block with four distinct caveats strung together, so a slightly more segmented structure would improve scanability.

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?

With no output schema, the description supplies the essential return contract (eligible/not-eligible/cant-check plus per-check evidence), the explicit limits of that verdict, the JavaScript execution limit, and the no-auth/no-cost fact. Nothing an agent needs to call it and interpret the result correctly appears to be missing.

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% and the single required 'url' parameter is already documented with an example format, so the schema carries the load. The description adds only 'one URL' (single-value, not batch) scoping, which is mildly useful but not syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb+resource+scope: check one URL against Google's stated conditions for being a supporting link in AI Overviews and AI Mode, and enumerates the exact signals examined (robots.txt, status, noindex, unavailable_after, nosnippet/max-snippet, data-nosnippet, canonical). That enumeration also separates it from siblings like ayrank_ai_crawler_access or ayrank_http_headers, which cover narrower slices.

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?

Opens with an explicit 'Use to...' framing and clearly bounds expectations: eligible never means included, it cannot tell whether a page is indexed ('only Search Console can'), and it does not check whether Google shows the page in an AI answer. What is missing is any in-catalog alternative to route to (e.g. when a sibling crawler-access check is the better call), so it is clear context rather than full when/when-not pairing.

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