alice

Compare AI visibility

compare_ai_visibility

Read-only

Compare how visible several websites are to AI answer engines, side by side. Scans 2-4 URLs and ranks them by AI visibility score, showing which blocks AI crawlers, which is server-rendered, and which has answer-ready structured data. Use when someone wants to benchmark their site against competitors, or asks why a competitor gets recommended by AI assistants and they do not. This compares technical readability only; it does not test live AI mentions.

Input Schema

Name	Required	Description	Default
`urls`	Yes	Two to four site URLs. Put the user’s own site first; results are returned ranked by score.
`locale`	No	Saved-report page language: en, zh-TW or ja. Independent of the scan market.	en
`country`	No	Scan market country code. Defaults to the page language’s market: us, tw or jp.
`language`	No	AI question/probe language code, e.g. en, zh-tw or ja. Defaults to the selected country’s language.

Output Schema

Name	Required	Description	Default
`rows`	Yes
`gated`	No
`next_step`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / country

Added value: +{
+  "description": "Scan market country code. Defaults to the page language’s market: us, tw or jp.",
+  "enum": [
+    "af",
+    "al",
+    "dz",
+    "ad",
+    "ao",
+    "ag",
+    "ar",
+    "am",
+    "au",
+    "at",
+    "az",
+    "bs",
+    "bh",
+    "bd",
+    "bb",
+    "be",
+    "bz",
+    "bj",
+    "bt",
+    "bo",
+    "ba",
+    "bw",
+    "br",
+    "bn",
+    "bg",
+    "bf",
+    "bi",
+    "kh",
+    "cm",
+    "ca",
+    "cv",
+    "cf",
+    "td",
+    "cl",
+    "cn",
+    "co",
+    "km",
+    "cg",
+    "cd",
+    "cr",
+    "ci",
+    "hr",
+    "cy",
+    "cz",
+    "dk",
+    "dj",
+    "dm",
+    "do",
+    "ec",
+    "eg",
+    "sv",
+    "gq",
+    "er",
+    "ee",
+    "sz",
+    "et",
+    "fj",
+    "fi",
+    "fr",
+    "ga",
+    "gm",
+    "ge",
+    "de",
+    "gh",
+    "gr",
+    "gd",
+    "gt",
+    "gn",
+    "gw",
+    "gy",
+    "ht",
+    "hn",
+    "hk",
+    "hu",
+    "is",
+    "in",
+    "id",
+    "iq",
+    "ie",
+    "il",
+    "it",
+    "jm",
+    "jp",
+    "jo",
+    "kz",
+    "ke",
+    "ki",
+    "kw",
+    "kg",
+    "la",
+    "lv",
+    "lb",
+    "ls",
+    "lr",
+    "ly",
+    "li",
+    "lt",
+    "lu",
+    "mg",
+    "mw",
+    "my",
+    "mv",
+    "ml",
+    "mt",
+    "mh",
+    "mr",
+    "mu",
+    "mx",
+    "fm",
+    "md",
+    "mc",
+    "mn",
+    "me",
+    "ma",
+    "mz",
+    "mm",
+    "na",
+    "nr",
+    "np",
+    "nl",
+    "nz",
+    "ni",
+    "ne",
+    "ng",
+    "mk",
+    "no",
+    "om",
+    "pk",
+    "pw",
+    "ps",
+    "pa",
+    "pg",
+    "py",
+    "pe",
+    "ph",
+    "pl",
+    "pt",
+    "qa",
+    "ro",
+    "rw",
+    "kn",
+    "lc",
+    "vc",
+    "ws",
+    "sm",
+    "st",
+    "sa",
+    "sn",
+    "rs",
+    "sc",
+    "sl",
+    "sg",
+    "sk",
+    "si",
+    "sb",
+    "so",
+    "za",
+    "kr",
+    "es",
+    "lk",
+    "sr",
+    "se",
+    "ch",
+    "tw",
+    "tj",
+    "tz",
+    "th",
+    "tl",
+    "tg",
+    "to",
+    "tt",
+    "tn",
+    "tr",
+    "tm",
+    "tv",
+    "ug",
+    "ua",
+    "ae",
+    "gb",
+    "us",
+    "uy",
+    "uz",
+    "vu",
+    "va",
+    "ve",
+    "vn",
+    "ye",
+    "zm",
+    "zw"
+  ],
+  "type": "string"
+}

addedInput schema / properties / language

Added value: +{
+  "description": "AI question/probe language code, e.g. en, zh-tw or ja. Defaults to the selected country’s language.",
+  "enum": [
+    "ps",
+    "sq",
+    "ar",
+    "ca",
+    "pt",
+    "en",
+    "es",
+    "hy",
+    "de",
+    "az",
+    "bn",
+    "nl",
+    "fr",
+    "dz",
+    "bs",
+    "pt-br",
+    "ms",
+    "bg",
+    "km",
+    "zh-cn",
+    "hr",
+    "el",
+    "cs",
+    "da",
+    "ti",
+    "et",
+    "am",
+    "fi",
+    "ka",
+    "zh-tw",
+    "hu",
+    "is",
+    "id",
+    "iw",
+    "it",
+    "ja",
+    "kk",
+    "ky",
+    "lo",
+    "lv",
+    "lt",
+    "dv",
+    "mt",
+    "ro",
+    "mn",
+    "sr",
+    "my",
+    "ne",
+    "mk",
+    "no",
+    "ur",
+    "pl",
+    "rw",
+    "sk",
+    "sl",
+    "so",
+    "ko",
+    "si",
+    "sv",
+    "tg",
+    "sw",
+    "th",
+    "tr",
+    "tk",
+    "uk",
+    "uz",
+    "vi"
+  ],
+  "type": "string"
+}

addedInput schema / properties / locale

Added value: +{
+  "default": "en",
+  "description": "Saved-report page language: en, zh-TW or ja. Independent of the scan market.",
+  "enum": [
+    "en",
+    "zh-TW",
+    "ja"
+  ],
+  "type": "string"
+}

First observedSep 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive and openWorld, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses the 2-4 URL scan scope, the ranking behavior, the three technical dimensions inspected, and a clear limitation (technical readability only, no live AI mention testing).

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?

Four sentences, each earning its place: purpose, output content, when-to-use triggers, and scope boundary. Front-loaded with the core purpose and no redundant 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?

An output schema exists and all four parameters are fully described in the schema, so the description need not cover return values. It covers purpose, usage and scope limits well; the only minor gap is that locale/country/language parameters are never mentioned, though the schema handles them adequately.

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%, so the schema already documents urls, locale, country and language thoroughly, including the 'own site first' convention and the locale/market independence. The description adds only the 'scans 2-4 URLs' restatement, so 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 (Compare) plus resource (AI visibility of websites), names the plural scope ('several websites... side by side'), and enumerates what it reports (crawler blocking, server-rendering, structured data). This implicitly and clearly separates it from the singular check_ai_visibility sibling.

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 two concrete triggers ('benchmark their site against competitors', 'asks why a competitor gets recommended') and an explicit scope exclusion ('does not test live AI mentions'). It does not, however, name check_ai_visibility as the alternative for single-site checks, so routing to the sibling is left to inference.

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

All alice tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?