Skip to main content
Glama

Fourward AI visibility tools

AI visibility check

check_ai_visibility
Read-onlyIdempotent

Scores how well AI search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) can reach, read and understand a website. Runs 75 checks in five groups: AI crawler access (robots.txt rules for 10 crawlers and a firewall test under five AI bot names), what pages tell machines without JavaScript, structured data, entity and authority (Wikipedia, Wikidata, review and social profiles, Reddit and Hacker News threads, brand search demand) and AI-ready content (readable prices, comparison and product pages, proof, docs, freshness). Returns a score out of 100, a grade, a score per group and every problem found, with the points it costs. Takes 10 to 30 seconds.

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

Input Schema

NameRequiredDescriptionDefault
domainYesThe website to check, as a domain such as example.com. A full URL also works; only the hostname is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: 75 checks across five named groups, a 10-30 second runtime, and the exact shape of the result (score out of 100, grade, per-group score, every problem with its point cost).

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?

One dense paragraph, front-loaded with the core purpose followed by scope, output shape and duration in a logical order. Nearly every clause carries information, though the five-group parenthetical is long and could be tighter.

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?

With no output schema, the description compensates by specifying the return values (score, grade, group scores, problem list with point costs) and the runtime. For a single-parameter read-only audit this is close to complete; only caching or re-run behavior is unaddressed.

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?

The single 'domain' parameter has 100% schema description coverage, including the note that a full URL works and only the hostname is used. The description adds nothing further about that parameter, so the schema does the work and 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?

Opens with a specific verb-plus-resource: scores how well AI search engines can reach, read and understand a website, and enumerates the five check groups so the scope is concrete. It does not explicitly state how it differs from the sibling check_ai_crawlers, though listing crawler access as only one of five groups implies the broader scope.

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

Usage Guidelines3/5

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

Usage is implied by the scope description plus the '10 to 30 seconds' runtime, which signals a heavyweight audit an agent should not call casually. However, there is no explicit guidance on when to prefer this over check_ai_crawlers, nor any exclusions or prerequisites.

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.

Resources