Skip to main content
Glama

Visibility Genies

Search Tripadvisor businesses

search_tripadvisor_businesses

Finds hotels, restaurants, attractions, and other businesses on Tripadvisor by name or category within a city or region, with rating, review count, category, and the url_path that get_tripadvisor_reviews takes. Usually completes within this call; a 'processing' response returns a taskId to call back with in 30-60 seconds at no extra cost. Estimated price: $0.01 for 30 results, billed per 30 at twice the Local page's normal-priority rate, so the call usually returns them. 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": "search_tripadvisor_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoNumber of results to collect (30-210). Defaults to 30. Billed per 30 results.
taskIdNoResume a previous call that returned status "processing". Pass back the taskId exactly as returned (format "tripadvisor_search:<id>"). Resuming charges no extra credits.
keywordNoBusiness name, category, or place to find on Tripadvisor (e.g. 'seafood restaurant'). Required unless resuming with taskId.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
locationCodeNoTripadvisor's own code for a city or region, as an alternative to locationName. The codes find_location returns are not Tripadvisor codes; pass locationName instead.
locationNameNoCity or region to search, as Tripadvisor names it: city, region and country, comma separated (e.g. "London,England,United Kingdom"). A name without its country is looked up in the project's country; a name Tripadvisor does not list is refused with the nearest names it does. Tripadvisor cannot search a whole country. Supply exactly one of locationName or locationCode unless resuming with taskId.
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
businessesNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the async processing model, the no-extra-cost taskId resume path, the per-30-results price and priority-rate multiplier, and the spend-cap hold/settle semantics including pre-purchase refusal. The readOnlyHint=false is consistent with a call that buys paid results and stages a task, so nothing is contradicted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and the cost-approval policy is explained, but the billing story is told twice ('billed per 30 at twice the Local page's normal-priority rate, so the call usually returns them' and again 'holds at most its estimate plus a margin... charged what it bought, never more'), and 'Usually completes within this call' is restated. Tightening would improve it.

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?

With an output schema present, the description need not explain returns, and it still covers the async path, resume behavior, and the paid-call guardrails that an agent needs to invoke this safely. For a 7-parameter, billed, potentially-async search tool, nothing essential is missing.

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 adds value by tying depth to per-30 billing and by describing the approvedMaxCostUsd escalation flow (ask the user, then retry with the approved amount). It is largely reinforcing what the schema already says rather than introducing new parameter meaning.

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 ('Finds') and resource (hotels, restaurants, attractions on Tripadvisor) plus the scoping by name/category within a city or region. It also names the return fields, including the url_path that get_tripadvisor_reviews consumes, which cleanly separates it from that sibling.

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?

Gives concrete operational guidance: it usually completes inline, a 'processing' result should be resumed with the taskId after 30-60 seconds, and a call refused over the spend limit requires asking the user before retrying with approvedMaxCostUsd. It does not explicitly contrast with other business-search siblings such as search_local_businesses or search_trustpilot_businesses, so the agent must infer the platform choice from the resource names.

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