Skip to main content
Glama

Citemark

Check AI visibility

check_ai_visibility
Read-only

Checks whether ChatGPT and Claude recommend a product when people ask which tool to use. It reads the product's homepage, writes 5 questions a buyer in its category would ask, asks each AI, and reports how often the product is named and in what position, which competitors are named instead, which websites the answers cite, three suggested fixes, and a link to the full shareable report. Takes about a minute. A site checked in the last 7 days returns that report instead of asking again.

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": {
      "website": "<website>"
    },
    "name": "check_ai_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYesThe product's website, like acme.com (a full URL works too).
categoryNoOptional: what kind of product it is, like 'uptime monitoring tool'. Read from the homepage when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds real value on top: approximate runtime ('about a minute'), the fact that it performs live external queries, and a caching rule where a site checked in the last 7 days returns the prior report instead of re-querying. It does not explain failure modes (unreachable homepage, rate limits, partial AI failures), which keeps it from 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?

Front-loaded with the core question it answers, then the mechanism, then the output contents, then the runtime and cache caveat. The output enumeration is long but each item tells the agent what it will get back. Minor tightening possible, but no sentence is filler.

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?

There is no output schema, so the description carries the return-value burden entirely, and it does: it lists coverage/position, named competitors, cited websites, three suggested fixes, and a shareable report link. Combined with runtime and caching disclosure, an agent has everything needed to call it and set expectations.

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%, so both parameters are already documented, including the fallback that category is read from the homepage when omitted. The description reinforces the role of category by describing questions written 'for a buyer in its category', but adds no format or constraint detail beyond the schema. 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?

The description opens with a specific verb and resource: it checks whether ChatGPT and Claude recommend a product, and it spells out the internal pipeline (reads homepage, writes 5 buyer questions, asks each AI). That makes the tool's function unmistakable and implicitly separates it from siblings like check_ai_crawlers or start_tracking. It stops short of naming or contrasting any alternative explicitly, so it lands at 4 rather than 5.

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 rather than stated: the reader can infer this is the tool for 'is my product recommended by AI assistants' questions. The 7-day cache note gives a useful hint against repeat calls for the same site, but there is no explicit when-to-use/when-not or routing to get_ai_picks or check_ai_crawlers for adjacent needs.

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