Crawlora MCP

tripcom_hotels_search

Read-only

Trip.com hotel search by city: normalized hotel summaries (name, location, star rating, guest rating, review count, image, display price) from a city's Trip.com hotel-list page.

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": {
      "city_slug": "<city_slug>",
      "city_id": "<city_id>"
    },
    "name": "tripcom_hotels_search"
  }
}

Input Schema

Name	Required	Description	Default
`city_id`	Yes	Trip.com numeric city id, the trailing number of a /hotels/{city_slug}-hotels-list-{city_id}/ URL, e.g. 359 for Bangkok.
`city_slug`	Yes	Trip.com city slug, the text segment of a /hotels/{city_slug}-hotels-list-{city_id}/ URL, e.g. bangkok.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that results are 'normalized hotel summaries' scraped from a city's hotel-list page, hinting that prices/availability are page-derived rather than live inventory, but it says nothing about pagination or result limits.

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?

A single front-loaded sentence that leads with the action and scope, then lists the payload. Every clause earns its place; nothing is padded or repeated.

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 an output schema present, the description need not explain return values, and it still summarizes them. Both required parameters are fully documented in the schema, so an agent has enough to call the tool correctly; only usage routing to the sibling detail tool is missing.

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%, and the two city parameters are documented in detail (URL-derived slug and numeric id with examples). The description adds no parameter-level meaning beyond 'by city', so the schema does the heavy lifting and the 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?

States a concrete verb+resource (hotel search on Trip.com) and even enumerates the returned summary fields (name, location, star rating, guest rating, review count, image, display price). It does not explicitly distinguish itself from the sibling tripcom_hotel_detail, but the city-level scope makes the intent unmistakable.

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?

The phrase 'by city' implies the usage context (city-level browse rather than a single-property lookup), which is a real constraint since both city_slug and city_id are required. However, it never names the alternative (tripcom_hotel_detail) or states when not to use this tool.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.