Skip to main content
Glama
ayrank-tools

ayrank-tools

Official
by ay-automate

AI training and grounding preferences

ayrank_ai_training_grounding
Read-only

Check a page's AI training and grounding permissions from Bing and Google-Extended directives. See whether Bingbot and Googlebot may crawl the path before you optimize.

Instructions

Use to read a page's AI training and grounding preferences: Bing AI Training (robots.txt __usage_ai-training group, page meta or X-Robots-Tag), Bing AI Grounding (page level), Google-Extended, and whether Bingbot and Googlebot may crawl the path. Only directives from Bing's and Google's 30 Oct 2026 posts. Not for the other AI crawlers (use ayrank_ai_crawler_access).

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_training_grounding"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description goes further by disclosing the actual data sources consulted (robots.txt __usage_ai-training group, page meta, X-Robots-Tag) and bounding the directive set to Bing's and Google's 30 Oct 2026 posts. It stops short of describing the response shape or how conflicting signals across sources are resolved, so not a 5.

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?

Two sentences, front-loaded with the purpose, then the exclusion. The parenthetical source list is dense but each item is substantive information about what is inspected. Slight compression cost in readability, but no filler.

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?

For a single-URL read tool with full annotation coverage, the description supplies scope, sources, and the sibling boundary. Because there is no output schema, the description should ideally sketch the returned fields; it only implies boolean crawlability and per-directive results, leaving return structure partly inferred.

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% and the single 'url' parameter is fully documented in the schema, so the schema carries the parameter burden. The description adds only that the URL denotes 'a page' to check, which is consistent but not new meaning — 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?

The description names a specific verb and resource (read a page's AI training and grounding preferences) and enumerates exactly which directives are covered: Bing AI Training, Bing AI Grounding, Google-Extended, and Bingbot/Googlebot path crawlability. It also explicitly distinguishes itself from ayrank_ai_crawler_access, so an agent can separate the two without opening either schema.

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?

The opening 'Use to read...' sets the context, and the closing sentence gives an explicit exclusion plus the correct alternative: 'Not for the other AI crawlers (use ayrank_ai_crawler_access).' This is a clear when-to-use / when-not-to-use pair with a named sibling.

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