Skip to main content
Glama
vantagemcp

vantage-mcp

by vantagemcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

check_ai_visibility

Read-onlyIdempotent

Check how often a specific domain appears in AI-generated answers on ChatGPT or Google AI Overview to assess brand visibility in AI search results.

Instructions

Check how many times a domain is cited in AI-generated answers on a given AI platform (chat_gpt, google). Use this to answer 'is my brand/domain visible in AI search' or 'does ChatGPT know about us'.

Read-only: no side effects, safe to retry. Costs 10 quota units/call (free tier: 3 checks/month total across all tools).

Returns: {"domain", "platform", "mentions_found" (int - how many times the domain was cited in the provider's tracked answers for this platform), "visible" (bool - true if mentions_found > 0)}.

Use find_citation_leaders instead if you want a ranked list of who's winning for a topic rather than one domain's own count. Use analyze_citation_trend instead if you want to see this count change over time rather than right now.

Args: domain: bare domain to check, e.g. "example.com" (no https://, no www). platform: "chat_gpt" or "google" (Google's AI Overview). Defaults to chat_gpt. Perplexity and Gemini aren't available - the underlying data provider doesn't cover them for this check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
platformNochat_gpt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive. The description reinforces these ('Read-only: no side effects, safe to retry') and adds cost information (10 quota units/call, free tier limit) and platform limitations. Return format is explicitly documented, covering behavior beyond annotations.

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?

The description is front-loaded with the core purpose, then moves to usage guidance, return format, and alternatives. Each sentence adds essential information for correct invocation—no filler or redundancy. The parameter explanations are integrated efficiently.

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?

Despite having no output schema, the description fully specifies the return object with field names and types. It also covers quota, platform coverage, and alternatives, providing everything an agent needs to decide on and execute the call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates. It explains the domain format requirements ('bare domain... no https://, no www') and enumerates the accepted platform values with a default and an explicit note on unavailable options. No parameter meaning is left to inference.

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 ('check how many times a domain is cited') and explicitly names the platforms supported. It also differentiates from siblings by name in the usage section, making the purpose unmistakable.

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?

Provides explicit when-to-use scenarios ('is my brand/domain visible in AI search') and directly names two alternative tools with the conditions that select them. Also clarifies platform availability (Perplexity and Gemini aren't covered), leaving no ambiguity.

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

Deploy Server

Other Tools