Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tripadvisor_reviews

Fetch TripAdvisor reviews for a place by ID or URL; filter by rating, language, sort, page, and limit to analyze feedback.

Instructions

Get TripAdvisor reviews. Returns reviews for a TripAdvisor place identified by id (location id) or url. limit defaults to 20 (max 50); page is 1-based; language, ratings (1 to 5) and sort_by refine the list. Each review has author, title, text, dates, rating, language, helpful votes, photos and URL. A page beyond total returns an empty reviews array.

Input 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

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavioral traits: the default limit of 20, the hard max of 50, 1-based pagination, and that a page beyond `total` returns an empty `reviews` array. It omits auth/permission needs and rate limits, but the pagination and default behavior are meaningfully surfaced.

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?

Front-loaded with purpose, then inputs, then defaults, then return shape, then an edge case — every sentence carries information. It is dense but not padded; slightly long, though each clause earns its place.

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, the description helpfully enumerates returned review fields (author, title, text, dates, rating, language, helpful votes, photos, URL) and covers the empty-page edge case. It is close to complete for a 10-parameter read tool, missing only auth and rate-limit context.

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 coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: it states `limit` defaults to 20 with a max of 50 (the schema only says 'Maximum reviews') and clarifies `ratings` spans 1 to 5 and that `page` is 1-based. These defaults and ranges are genuinely additive.

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+resource ('Get TripAdvisor reviews') and names the identifier inputs (id/url) that distinguish it from sibling tools like tripadvisor_place and tripadvisor_search. An agent can identify this as the review-fetching tool without opening the 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?

The description implies usage by explaining the id-or-url identifier and refinement filters, but never states when to choose this over siblings (tripadvisor_place, tripadvisor_hotels) or any prerequisite/exclusion. Usage is inferable but not explicit.

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