Skip to main content
Glama

Site SEO & AI Crawler Audit

Check AI crawler access in robots.txt

check_ai_crawler_access
Read-onlyIdempotent

Checks whether 14 AI crawlers may fetch a page. Use it when the user asks whether AI crawlers can read a website or page, for example "can AI crawlers read example.com?", "is GPTBot blocked in my robots.txt?" or "which AI bots are allowed on https://example.com/blog?". Pass the page address. Returns, for 14 AI crawlers, whether robots.txt allows the page and the rule that decided it, plus the sitemaps, the redirect chain, and the page's X-Robots-Tag header and robots meta tag. It requests the page as ChatGPT-User, OAI-SearchBot, GPTBot, ClaudeBot, PerplexityBot and a browser, and says if ChatGPT can read it in one verdict (readable, blocked by CDN or WAF, blocked by robots, needs JavaScript, redirect problem, needs sign-in) with the fix. That test is by user agent from Agent Tools servers, not from OpenAI's addresses. Do not use it for private or local addresses, for security scans, or to collect a site's content.

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": "check_ai_crawler_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAddress of a public web page, for example https://example.com/pricing. A bare domain such as example.com means https. Only public http and https sites on the standard ports are checked.

Output Schema

NameRequiredDescriptionDefault
urlYesThe address checked, after a bare domain became https.
notesNoPlain-language caveats to pass on with the result.
noticeYesAs-of caveat: what the site sent to Agent Tools at that moment, not what every crawler sees.
robotsNo
sourceYesWhere the data came from: the website itself.
statusNoHTTP status code of the final page.
failureNoWhy the page was not reached or read, such as a timeout or a refused redirect.
crawlersNo
finalUrlNoAddress of the final page after redirects.
reachableYesFalse when no page answered; failure then says why.
redirectsNoRedirect chain from the address to the page.
metaRobotsNoThe page's robots meta tag.
xRobotsTagNoThe page's X-Robots-Tag response header.
blockedCrawlersNoTokens of the crawlers robots.txt blocks on this page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / robots / properties / status / description
      Previous value: -"found: rules were read. missing: a 4xx answer, so nothing is restricted. unreachable: a 5xx or no answer, so there is no verdict."New value: +"found: rules were read. missing: a 4xx answer, so nothing is restricted. unreachable: a 5xx, no answer, or a web page instead of a robots file, so there is no verdict."
  2. Changed24 schema fields changed
    • addedOutput schema / properties / blockedCrawlers / description
      Added value: +"Tokens of the crawlers robots.txt blocks on this page."
    • addedOutput schema / properties / crawlers / items / properties / allowed / description
      Added value: +"Whether robots.txt allows this crawler on the page. null means robots.txt could not be read, so there is no verdict."
    • addedOutput schema / properties / crawlers / items / properties / crawler / description
      Added value: +"User-agent token, such as GPTBot."
    • addedOutput schema / properties / crawlers / items / properties / operator / description
      Added value: +"Company that runs the crawler."
    • addedOutput schema / properties / crawlers / items / properties / purpose / description
      Added value: +"What the crawler collects for, such as training or search."
    • addedOutput schema / properties / crawlers / items / properties / rule / description
      Added value: +"The robots.txt line that decided it, such as Disallow: /."
    • addedOutput schema / properties / failure / description
      Added value: +"Why the page was not reached or read, such as a timeout or a refused redirect."
    • addedOutput schema / properties / finalUrl / description
      Added value: +"Address of the final page after redirects."
    • addedOutput schema / properties / metaRobots / description
      Added value: +"The page's robots meta tag."
    • addedOutput schema / properties / notes / description
      Added value: +"Plain-language caveats to pass on with the result."
    • addedOutput schema / properties / notice / description
      Added value: +"As-of caveat: what the site sent to Agent Tools at that moment, not what every crawler sees."
    • addedOutput schema / properties / reachable / description
      Added value: +"False when no page answered; failure then says why."
    • addedOutput schema / properties / redirects / description
      Added value: +"Redirect chain from the address to the page."
    • addedOutput schema / properties / redirects / items / properties / location / description
      Added value: +"Location header of a redirect hop: where it points next."
    • addedOutput schema / properties / redirects / items / properties / status / description
      Added value: +"HTTP status code of this hop, such as 301 or 200."
    • addedOutput schema / properties / redirects / items / properties / url / description
      Added value: +"Address requested at this hop."
    • addedOutput schema / properties / robots / properties / httpStatus / description
      Added value: +"HTTP status code of robots.txt."
    • addedOutput schema / properties / robots / properties / sitemaps / description
      Added value: +"Sitemap addresses listed in robots.txt."
    • addedOutput schema / properties / robots / properties / status / description
      Added value: +"found: rules were read. missing: a 4xx answer, so nothing is restricted. unreachable: a 5xx or no answer, so there is no verdict."
    • addedOutput schema / properties / robots / properties / url / description
      Added value: +"Address of robots.txt."
    • addedOutput schema / properties / source / description
      Added value: +"Where the data came from: the website itself."
    • addedOutput schema / properties / status / description
      Added value: +"HTTP status code of the final page."
    • addedOutput schema / properties / url / description
      Added value: +"The address checked, after a bare domain became https."
    • addedOutput schema / properties / xRobotsTag / description
      Added value: +"The page's X-Robots-Tag response header."
  3. Changed1 schema field changed
    • removedOutput schema / properties / note_from_openkrill
      Removed value: -{
      -  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      -  "type": "string"
      -}
  4. Changed1 schema field changed
    • addedOutput schema / properties / note_from_openkrill
      Added value: +{
      +  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the read-only/idempotent/openWorld annotations: it discloses that the fetch is performed as ChatGPT-User, OAI-SearchBot, GPTBot, ClaudeBot, PerplexityBot and a browser, and warns that the test comes from Agent Tools servers rather than OpenAI's addresses. It also pre-explains the verdict taxonomy (CDN/WAF, robots, JavaScript, redirect, sign-in), which prevents misreading of failures.

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 purpose, then usage, then behavior caveats, and every sentence carries information. It is somewhat long, and the detailed return-value enumeration is partly redundant given an output schema exists.

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 open-world read tool with an output schema, the description covers trigger conditions, exclusions, the user agents used, the environment caveat, and how to interpret verdicts. Nothing needed 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with the url parameter already documenting the bare-domain-means-https and public-standard-port rules. The description only adds "Pass the page address," so the schema does the substantive work and the 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 and resource ("Checks whether 14 AI crawlers may fetch a page") with an explicit scope of 14 crawlers. It is clearly distinguishable from siblings like trace_redirects or check_page_tags, which do not cover crawler-permission verdicts.

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?

Gives concrete trigger queries ("can AI crawlers read example.com?", "is GPTBot blocked in my robots.txt?") and explicit when-not cases: private/local addresses, security scans, or content collection. It does not name a sibling alternative to use instead, so it falls short of a full 5.

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.