Crawlora MCP

tripadvisor_autocomplete

Read-only

Return TripAdvisor typeahead suggestions for partial text, including candidate names and places. Use tripadvisor_search when you have a complete query and want search results, or tripadvisor_place for details about one known place.

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": {
      "q": "<q>"
    },
    "name": "tripadvisor_autocomplete"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Required. Search text to autocomplete, e.g. hong kong.
`type`	No	Optional result-type filter. Allowed values: hotel, restaurant, attraction.
`limit`	No	Max number of candidates to return.
`locale`	No	Locale code, e.g. en-HK, en-US, en-GB.
`route_uid`	No	Advanced replay-only route uid; not required for normal use.
`scope_geo_id`	No	Optional TripAdvisor geo id to scope suggestions to a location.
`typeahead_id`	No	Advanced replay-only typeahead id; not required for normal use.
`search_session_id`	No	Advanced replay-only search session id; not required for normal use.

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 5, 2026

TDQS

A4.3/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, and an output schema exists. The description adds that input is partial text and output is candidate names and places, but gives no return-format, pagination, or rate-limit context. Adequate but modest value beyond structured fields.

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?

Two sentences, zero waste, purpose front-loaded ahead of the disambiguation guidance. Every clause earns its place.

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?

With a full output schema, complete parameter coverage, and annotations carrying the safety profile, the remaining need is purpose and routing, both of which are present. Nothing required to call the tool correctly 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%, so the schema already documents all eight parameters, including the advanced replay-only fields. The description only implies the partial-text nature of 'q' and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Return TripAdvisor typeahead suggestions') with a clear scope ('for partial text'), and names the sibling tools it is distinct from. An agent can tell it apart from tripadvisor_search and tripadvisor_place without opening any schema.

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?

Explicitly routes the agent: use tripadvisor_search for a complete query and tripadvisor_place for details about one known place. The when-to-use condition (partial text vs. complete query) is stated, not left to inference.

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.

Resources

Need Help?