Skip to main content
Glama
hhw67865

TripAdvisor Vacation Planner MCP Server

by hhw67865

search_locations

Find TripAdvisor locations by search query and optional category filter to plan vacation activities, accommodations, and dining.

Instructions

Search for locations on TripAdvisor

Args:
    query: Search term (e.g., "hotels in Paris")
    category: Optional category filter (e.g., "hotels", "restaurants", "attractions")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
categoryNo

Implementation Reference

  • The main handler for the 'search_locations' tool. Decorated with @mcp.tool() for registration. Defines input schema via type hints and docstring. Executes search by calling TripAdvisor API via helper function.
    @mcp.tool()
    async def search_locations(query: str, category: Optional[str] = None) -> str:
        """
        Search for locations on TripAdvisor
        
        Args:
            query: Search term (e.g., "hotels in Paris")
            category: Optional category filter (e.g., "hotels", "restaurants", "attractions")
        """
        params = {"searchQuery": query}
        if category:
            params["category"] = category
        
        result = await tripadvisor_api_request("location/search", params)
        return json.dumps(result, indent=2)
  • Supporting helper function that handles API requests to TripAdvisor, used by the search_locations tool and other tools.
    async def tripadvisor_api_request(endpoint: str, params: Dict[str, Any] = None) -> Dict[str, Any]:
        """Make a request to the TripAdvisor API"""
        if not TRIPADVISOR_API_KEY:
            return {"error": "TripAdvisor API key not configured. Set TRIPADVISOR_API_KEY environment variable."}
        
        headers = {"accept": "application/json", "key": TRIPADVISOR_API_KEY}
    
        if params is None:
            params = {}
    
        params["key"] = TRIPADVISOR_API_KEY
    
        url = f"{API_BASE_URL}/{endpoint}"
        
        async with httpx.AsyncClient() as client:
            try:
                response = await client.get(url, headers=headers, params=params, timeout=30.0)
                response.raise_for_status()
                return response.json()
            except httpx.HTTPStatusError as e:
                return {
                    "error": f"HTTP error occurred: {e}",
                    "details": str(e)
                }
            
    #Resources for specific location details
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the search functionality but doesn't describe important behavioral aspects like whether results are paginated, what format they return, rate limits, authentication requirements, or error conditions. This leaves significant gaps for an agent trying to use the tool effectively.

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 description is appropriately sized and front-loaded with the core purpose. The parameter explanations are concise with helpful examples. The structure is logical with a clear heading for arguments, though it could be slightly more polished in formatting.

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?

For a search tool with 2 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the search returns (list of locations? with what fields?), how results are ordered, whether there are limitations on query length, or any error handling. The parameter semantics are well-explained, but other critical context 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?

The description provides clear semantic meaning for both parameters with helpful examples ('hotels in Paris', 'hotels', 'restaurants', 'attractions'), which adds significant value beyond the 0% schema description coverage. The examples clarify how to format the query and what categories might be acceptable, compensating well for the lack of schema descriptions.

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?

The description clearly states the verb ('Search') and resource ('locations on TripAdvisor'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_nearby_locations' or 'plan_vacation', which would require more specific scope definition.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_nearby_locations' or 'plan_vacation'. The description only explains what the tool does, not when it's appropriate or what distinguishes it from other search/filtering tools in the same server.

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/hhw67865/tripadvisor-mcp-server'

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