Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tripadvisor_autocomplete

Get TripAdvisor autocomplete suggestions for locations, hotels, restaurants, and attractions from a query, with optional locale, type, and geo filters.

Instructions

Autocomplete TripAdvisor locations and places. Returns TripAdvisor typeahead suggestions for the required query q, optionally narrowed by limit, locale, scope_geo_id and a type hint. Each result has its id, title, type, URL, image, parent location and coordinates, and may carry nested search shortcuts. Results can be locations, hotels, restaurants or attractions.

Input Schema

NameRequiredDescriptionDefault
qYesAutocomplete query
typeNoOptional result type hint
limitNoMaximum results
localeNoTripAdvisor locale
route_uidNoOptional captured route uid
scope_geo_idNoOptional scoped geo id
typeahead_idNoOptional captured typeahead id
search_session_idNoOptional captured search session id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose meaningful return behavior: each result carries id, title, type, URL, image, parent location, coordinates, and possibly nested search shortcuts. It implicitly signals a safe read (returns suggestions), though it says nothing about auth, rate limits, or result caps.

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?

Three front-loaded sentences: purpose first, then narrowing parameters, then result shape. No filler. It is slightly longer than strictly needed given the schema already carries parameter detail, but every sentence maps to useful information.

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 and no annotations, the description compensates by describing both the input narrowing options and the returned fields. An agent has enough to call it and interpret the response; only auth/rate-limit context 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. The description names q, limit, locale, scope_geo_id and the type hint, but omits route_uid, typeahead_id and search_session_id and adds no format or semantics beyond the schema's one-liners. 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 (autocomplete) and resource (TripAdvisor locations and places), and enumerates the result kinds (locations, hotels, restaurants, attractions). This clearly distinguishes it from siblings like tripadvisor_search or 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'typeahead suggestions for the required query q' suggests a lookup/typeahead role, and the result types hint at downstream calls. There is no explicit when-to-use statement, no mention of the alternative tripadvisor_search, and no guidance on when to prefer one over the other.

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