Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

AI crawler access

ayrank_ai_crawler_access
Read-only

Check if GPTBot, ClaudeBot, PerplexityBot and Google-Extended may crawl a homepage via robots.txt, meta robots and X-Robots-Tag; returns allowed/blocked per bot with the deciding line.

Instructions

Use to check whether GPTBot, ClaudeBot, PerplexityBot and Google-Extended may crawl a site's homepage under its robots.txt, plus the homepage's meta robots and X-Robots-Tag rules for them. Returns allowed or blocked per bot with the deciding line. Not for one specific page or another user agent (use ayrank_robots_txt_test), and it cannot see CDN or firewall rules that fire only for the real bots, because it sends an AY Rank user agent. 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": {
      "domain": "<domain>"
    },
    "name": "ayrank_ai_crawler_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe site, like example.com. A full URL works; only its host is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark it read-only and open-world, but the description adds substantive context beyond them: it sends an AY Rank user agent (so firewall/CDN results are not representative), it does not execute JavaScript, and it requires no API key. It also discloses what a result contains (per-bot verdict plus the deciding line), which is real behavioral value.

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

Conciseness5/5

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

Dense but front-loaded: the purpose and scope come first, then the return format, then exclusions, then the two behavioral caveats. Every sentence carries information an agent needs and none is redundant with the schema or annotations.

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 single-parameter read tool with no output schema, the description covers the purpose, the exact response shape, the exclusions, and the two failure modes (spoofed user agent, no JS execution) that could otherwise cause a misread result. Nothing an agent needs to call it correctly is missing.

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% and the single domain parameter is fully documented in the schema, so the baseline is 3. The description adds meaningful scope: the check targets the homepage only, which tells the agent that the domain parameter is used at host level even for deep pages. No syntax detail is added beyond that, so it sits slightly above baseline rather than at the top.

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 and resource: checking whether four named AI bots (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) may crawl a site's homepage under robots.txt, meta robots and X-Robots-Tag. It also declares the return shape (allowed/blocked per bot with the deciding line), so it is distinguishable from sibling robots tools at a glance.

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

Usage Guidelines5/5

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

Explicitly names the excluded case and the alternative: not for one specific page or another user agent, use ayrank_robots_txt_test instead. It also sets expectations about what the check cannot detect (CDN/firewall rules that only fire for real bots), which is a usage boundary an agent must know before deciding to call it.

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