Skip to main content
Glama
pab1it0

Tripadvisor MCP

get_location_reviews

Retrieve user reviews for a specific Tripadvisor location to assess visitor experiences and ratings.

Instructions

Get reviews for a specific location

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationIdYes
languageNoen

Implementation Reference

  • The main handler function decorated with @mcp.tool for registration. Implements the logic to fetch reviews for a Tripadvisor location by making an API request to the reviews endpoint.
    @mcp.tool(description="Get reviews for a specific location")
    async def get_location_reviews(
        locationId: Union[str, int],
        language: str = "en",
    ) -> Dict[str, Any]:
        """
        Get the most recent reviews for a specific location.
        
        Parameters:
        - locationId: Tripadvisor location ID (can be string or integer)
        - language: Language code (default: 'en')
        """
        params = {
            "language": language,
        }
        
        # Convert locationId to string to ensure compatibility
        location_id_str = str(locationId)
        
        return await make_api_request(f"location/{location_id_str}/reviews", params)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action without detailing traits like whether it's read-only, requires authentication, has rate limits, returns paginated results, or includes error handling. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 description is extremely concise with a single sentence that directly states the tool's purpose. It is front-loaded and wastes no words, making it easy to parse quickly. This efficiency is appropriate for a simple tool, though it sacrifices detail for brevity.

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

Completeness2/5

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

Given the tool's complexity (2 parameters, no output schema, no annotations), the description is incomplete. It does not cover parameter meanings, behavioral traits, or output expectations (e.g., review format, error cases). Without annotations or an output schema, the description fails to provide enough context for reliable agent use.

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

Parameters2/5

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

The schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'a specific location' but does not explain the 'locationId' parameter (e.g., format, source) or the optional 'language' parameter (e.g., supported codes, default behavior). This lack of semantic context leaves parameters ambiguous beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get reviews for a specific location' clearly states the action (get) and resource (reviews for a location), which is adequate. However, it lacks specificity about what 'reviews' entail (e.g., ratings, comments, dates) and does not differentiate from sibling tools like 'get_location_details' or 'get_location_photos', leaving ambiguity about the scope of information returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a location ID), exclusions, or comparisons to siblings such as 'search_locations' for broader queries. This absence of context makes it harder for an agent to select the correct tool in practice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pab1it0/tripadvisor-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server