Skip to main content
Glama

Nicolas Sitter Research

get_ai_hotel_visibility

Read-only

Get the hotels an AI platform actually recommends for a destination in a given week, ranked by how often it mentions them, with the split of links it gives each one (direct to the hotel, to an OTA, to a chain site, or elsewhere). Use this when the user asks which hotels ChatGPT or Gemini or Perplexity recommends in a city, whether a specific hotel or brand shows up in AI answers, who is winning AI visibility in a market, or how a destination's results differ between platforms. Get platform ids and city slugs from get_ai_hotel_landscape_manifest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_ai_hotel_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity slug or name, e.g. "paris". Omit for all destinations.
weekNoSnapshot week as YYYY-MM-DD. Omit for the most recent.
clientNoOptional: identify yourself, e.g. "my-agent/1.0". Not required and never used by the tool itself — recorded only so the public tracker at /projects/agent-tools can measure how many callers self-identify when nothing forces them to.
platformNoPlatform id from the manifest, e.g. "chatgpt". Omit for all platforms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already state readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior, since it explains the ranking basis, link-split taxonomy, and weekly snapshot grain. However, it does not say how many hotels are returned or what the response shape is for each hotel.

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?

The definition is front-loaded with purpose then use cases then prerequisite, and every sentence carries information. The middle sentence is a long run-on list of triggers that could be tightened, but no sentence is 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?

There is no output schema, so the description does well to spell out the return content (ranked hotels, mention counts, link splits). Missing: result limits, whether the ranking is absolute or normalized, and what an empty destination returns. These are minor for a read-only query tool.

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 defines city, week, platform, and client, so the baseline is a 3. The description adds real value by naming get_ai_hotel_landscape_manifest as the source of valid platform ids and city slugs. Nothing else is added about formats or defaults.

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 says it returns hotels an AI platform actually recommends for a destination in a given week, ranked by mention frequency, with the split of links (direct, OTA, chain, elsewhere). That is a specific verb, resource, and ranking dimension, and it clearly differs from the brand-level sibling get_hotel_brand_leaderboard.

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?

It explicitly lists four triggers: which hotels ChatGPT/Gemini/Perplexity recommends in a city, whether a specific hotel or brand shows up, who is winning AI visibility in a market, or how a destination's results differ across platforms. It also states the prerequisite that platform ids and city slugs must come from get_ai_hotel_landscape_manifest first.

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