Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tripadvisor_reviews

Fetch normalized TripAdvisor public reviews from credential-free GraphQL data using a location ID or place URL, with rating, language, sort, page, and photo filters.

Instructions

Get TripAdvisor reviews. Returns normalized TripAdvisor public reviews from credential-free GraphQL review data. Pass either id or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoTripAdvisor location id
urlNoTripAdvisor place URL
pageNo1-based review page
limitNoMaximum reviews
ratingsNoRating filters
sort_byNoLegacy sort field; DATE selects newest first, FAVORABLE_RATING uses upstream order
languageNoReview language
sort_typeNoLegacy sort type; DEFAULT selects newest first, ML_SORTED uses upstream order unless sort_by is DATE
do_machine_translationNoEnable upstream machine translation
photos_per_review_limitNoMaximum photos per review

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.17.9
    • addedInput schema / properties / ratings / items / enum
      Added value: +[
+  1,
+  2,
+  3,
+  4,
+  5
+]
    • changedInput schema / properties / sort_by / description
      Previous value: -"Review sort field"New value: +"Legacy sort field; DATE selects newest first, FAVORABLE_RATING uses upstream order"
    • addedInput schema / properties / sort_by / enum
      Added value: +[
+  "FAVORABLE_RATING",
+  "DATE"
+]
    • changedInput schema / properties / sort_type / description
      Previous value: -"Review sort type"New value: +"Legacy sort type; DEFAULT selects newest first, ML_SORTED uses upstream order unless sort_by is DATE"
    • addedInput schema / properties / sort_type / enum
      Added value: +[
+  "ML_SORTED",
+  "DEFAULT"
+]
  2. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / ratings / items
      Added value: +{
+  "type": "integer"
+}
  3. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/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. It usefully discloses that the data comes from credential-free GraphQL public reviews, implying no auth is needed, but it says nothing about pagination behavior, rate limits, or what the normalized response contains.

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 short sentences, zero waste, with the purpose front-loaded and the input rule immediately after. Everything earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a review-fetching tool with 10 parameters, no output schema, and no annotations, the description covers the essentials (what it does, how to supply input) but omits return shape, pagination, and the relationship to sibling tools. The rich schema compensates for parameter gaps, but behavioral coverage is thin.

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?

Schema description coverage is 100%, so baseline is 3. The description adds genuine value beyond the schema by clarifying that id and url are alternatives ('pass either id or url'), which resolves the ambiguity created by both being optional and non-required.

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?

Clear verb+resource: 'Get TripAdvisor reviews', plus scope detail on how the data is sourced and returned. It names the resource specifically, though it does not differentiate this tool from its close sibling tripadvisor_place (both fetch TripAdvisor content), leaving some ambiguity about which to pick.

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?

'Pass either id or url' gives the primary input-selection rule, which is useful given both params are optional. However there is no guidance on when to use this tool versus tripadvisor_place, tripadvisor_search, or tripadvisor_autocomplete – usage is only implied.

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