Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tripcom_hotels_search

Search Trip.com hotels by city using exact city_slug and city_id values. Get hotel names, locations, star ratings, guest ratings, review counts, images, and display prices from a city hotel-list page.

Instructions

Search Trip.com hotels by city. Returns Trip.com's own top-hotels page for a city: hotel summaries (name, location, star rating, guest rating, review count, image, display price) for the hotels Trip.com features on that city's hotel-list page. Trip.com does not expose a free-text city search, so callers supply the exact city_slug and city_id pair from a known Trip.com hotel-list URL of the form https://www.trip.com/hotels/{city_slug}-hotels-list-{city_id}/.

Input Schema

NameRequiredDescriptionDefault
city_idYesTrip.com numeric city id, the trailing number of a /hotels/{city_slug}-hotels-list-{city_id}/ URL
city_slugYesTrip.com city slug, the text segment of a /hotels/{city_slug}-hotels-list-{city_id}/ URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the data source (Trip.com's own top-hotels page, not an exhaustive search) and the exact fields returned. It omits auth requirements, rate limits, and pagination, but for a read-only list endpoint those are minor.

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?

Three sentences, front-loaded with the purpose, then the return shape, then the critical input constraint. No filler and each sentence earns its place.

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, explaining the return payload is the right call and it does so concretely. The definition is complete enough to call the tool correctly; the only gap is the absence of any routing guidance relative to sibling hotel tools.

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% and both schema descriptions already explain that the values come from a /hotels/{city_slug}-hotels-list-{city_id}/ URL, so the description largely repeats that. It usefully ties the two parameters together as a required pair, but adds no syntax or format detail beyond the schema.

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?

States a specific verb+resource ('Search Trip.com hotels by city') and explicitly enumerates the returned fields (name, location, star rating, guest rating, review count, image, display price). It implicitly distinguishes itself from tripcom_hotel_detail by describing a city-level list of hotel summaries, though it never names that 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 a strong, actionable constraint: callers must supply the exact city_slug/city_id pair from a known Trip.com hotel-list URL, because Trip.com has no free-text city search. It tells the agent what not to attempt, but does not list alternatives (e.g., tripcom_hotel_detail) or when to prefer them.

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