Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tripadvisor_enums

Retrieve TripAdvisor filter enums and IDs for locales, currencies, sorts, amenities, restaurant options, and attraction categories to build or validate searches. No input required.

Instructions

Get TripAdvisor enum metadata. Returns the values TripAdvisor place and listing filters accept: locales, currencies, languages, listing_types, sorts, pricing_modes, hotel_classes, hotel_amenities, restaurant_types, restaurant_options, attraction categories with their ids, and filter_ids. It also lists unsupported_entity_types. Takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses that the tool takes no parameters and lists the full set of returned enum groups plus unsupported_entity_types. It does not discuss auth or rate limits, but for a simple metadata read those omissions 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?

The purpose is front-loaded, and the following enumeration is dense but necessary to tell the agent exactly which enum families are available. No sentence is wasted.

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?

For a no-param metadata tool with no output schema and no annotations, the description is nearly complete: it names every returned enum family and unsupported_entity_types. It does not spell out the exact response structure, which is a minor gap but not a blocker for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, and the description explicitly says "Takes no parameters." The schema is empty, so the no-param baseline applies; the description confirms this rather than adding parameter syntax.

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 opens with a specific verb and resource ("Get TripAdvisor enum metadata") and enumerates the exact enum families returned. This clearly separates it from sibling search/detail tools such as tripadvisor_search and tripadvisor_place, which consume these values rather than produce them.

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?

It states that the values are what TripAdvisor place and listing filters accept, giving clear context for when to call it. However, it does not explicitly name alternatives or state when not to use it, so it lacks a complete routing rule.

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