Skip to main content
Glama

Visibility Genies

Get Tripadvisor reviews

get_tripadvisor_reviews

Collects Tripadvisor reviews for one listing, with rating, author, visit date, text, and whether the owner responded. Use it for review-gap analysis against competitors and to spot unanswered reviews; find the listing's url_path with search_tripadvisor_businesses first. Usually completes within this call; if the queued job is still running you get status 'processing' plus a taskId, so call again with that taskId in 30-60 seconds to collect the result at no extra cost. Estimated price: $0.01 for 20 reviews, billed per 10 at twice the Local page's normal-priority rate, so the call usually returns them; reviews bought within a day, here or on the Local page, are answered at no charge. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_tripadvisor_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoNumber of reviews to collect (10-200). Defaults to 20. Billed per 10 reviews.
sortByNoReview sort order. Defaults to most_recent.
taskIdNoResume a previous call that returned status "processing". Pass back the taskId exactly as returned (format "tripadvisor_reviews:<id>"). Resuming charges no extra credits.
urlPathNoThe listing's url_path from search_tripadvisor_businesses rows (a full Tripadvisor listing link also works). Required unless resuming with taskId.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
statusYes
taskIdYes
totalsNo
reviewsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Far beyond the annotations, the description discloses the async job model, that a 'processing' status plus taskId can be resumed at no extra cost after 30-60 seconds, the pricing rate, and the spend-limit hold/charge mechanics with refusal semantics. The only shortfall is that cost arithmetic is dense and partly repeated (the $0.01/20-reviews example vs. per-10 billing).

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?

The purpose and prerequisite are front-loaded in the first two sentences, and each later sentence carries operational content. The cost paragraphs are long and restate the same billing idea twice, which trims a point but does not obscure the call flow.

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?

For a paid, possibly-asynchronous, open-world tool with six parameters, the description covers entry (urlPath prerequisite), long-running behavior and resumption, cost and spend-limit approval, and failure handling. An output schema exists, so the lack of return-value detail is not a gap.

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 the baseline is 3; the description nevertheless adds useful meaning by tying taskId to the 'processing' status and the wait window, tying urlPath to the search_tripadvisor_businesses output, and explaining that approvedMaxCostUsd is only ever used after a refusal and only with user approval.

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 opening sentence states a specific verb and resource (collects Tripadvisor reviews for one listing) and enumerates the returned fields (rating, author, visit date, text, owner response), which distinguishes it from siblings like get_business_reviews and get_trustpilot_reviews by platform and payload.

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?

It names concrete use cases (review-gap analysis against competitors, spotting unanswered reviews) and an explicit prerequisite: obtain url_path from search_tripadvisor_businesses first. It also states the refusal condition and the approval path, so the agent knows when it must ask the user before retrying.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources