Skip to main content
Glama
harimkang

Korea Tourism API MCP Server

search_tourism_by_keyword

Search Korea Tourism Organization database for attractions, events, restaurants, and accommodations by keyword, with filtering by content type, area, and language.

Instructions

Search for tourism information in Korea by keyword.

This tool searches through the Korea Tourism Organization database for tourism items matching the specified keyword. It supports filtering by content type, area, and provides paginated results with detailed information.

Args: keyword (str): Search keyword (e.g., "Gyeongbokgung", "Hanok", "Bibimbap") content_type (str, optional): Type of content to search for. Valid values: - "Tourist Attraction" (default) - "Cultural Facility" - "Festival Event" - "Leisure Activity" - "Accommodation" - "Shopping" - "Restaurant" - "Transportation" area_code (str, optional): Area code to filter results. Valid values: - "1" (Seoul) - "2" (Incheon) - "3" (Daejeon) - "4" (Daegu) - "5" (Gwangju) - "6" (Busan) - "7" (Ulsan) - "8" (Sejong) - "31" (Gyeonggi-do) - "32" (Gangwon-do) - "33" (Chungcheongbuk-do) - "34" (Chungcheongnam-do) - "35" (Gyeongsangbuk-do) - "36" (Gyeongsangnam-do) - "37" (Jeonbuk-do) - "38" (Jeollanam-do) - "39" (Jeju-do) language (str, optional): Language for results (default: "en"). Supported: - "en" (English) - "jp" (Japanese) - "zh-cn" (Simplified Chinese) - "zh-tw" (Traditional Chinese) - "de" (German) - "fr" (French) - "es" (Spanish) - "ru" (Russian) page (int, optional): Page number for pagination (default: 1, min: 1) rows (int, optional): Number of items per page (default: 20, max: 100) filter (list[str], optional): List of keys to include in each result item (whitelist). - If filter is None or an empty list ([]), all fields are returned. - If filter contains values, only the specified keys will be included in each item, and all other keys will be removed.

Returns: dict: Search results with structure: { "total_count": int, # Total number of matching items "num_of_rows": int, # Number of items per page "page_no": int, # Current page number "items": [ # List of tourism items { "title": str, # Name of the attraction/place "addr1": str, # Primary address "addr2": str, # Secondary address "areacode": str, # Area code "sigungucode": str, # Sigungu code "cat1": str, # Category 1 code "cat2": str, # Category 2 code "cat3": str, # Category 3 code "contentid": str, # Unique content ID "contenttypeid": str, # Content type ID "createdtime": str, # Creation timestamp "modifiedtime": str, # Last modified timestamp "tel": str, # Phone number "firstimage": str, # URL of main image "firstimage2": str, # URL of thumbnail image "mapx": str, # Longitude "mapy": str, # Latitude "mlevel": str, # Map level "cpyrhtDivCd": str # Copyright division code } # ... more items ] }

Example: search_tourism_by_keyword("Gyeongbokgung", "Tourist Attraction", "1", "en", 1, 10)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes
content_typeNo
area_codeNo
languageNo
pageNo
rowsNo
filterNo

Implementation Reference

  • The implementation of the search_tourism_by_keyword tool, which handles the logic for searching tourism information by keyword from the Korea Tourism Organization API.
    async def search_tourism_by_keyword(
        keyword: str,
        content_type: str | None = None,
        area_code: str | None = None,
        language: str | None = None,
        page: int = 1,
        rows: int = 20,
        filter: List[str] | None = None,
    ) -> dict:
        """
        Search for tourism information in Korea by keyword.
    
        This tool searches through the Korea Tourism Organization database for tourism items
        matching the specified keyword. It supports filtering by content type, area, and
        provides paginated results with detailed information.
    
        Args:
            keyword (str): Search keyword (e.g., "Gyeongbokgung", "Hanok", "Bibimbap")
            content_type (str, optional): Type of content to search for. Valid values:
                - "Tourist Attraction" (default)
                - "Cultural Facility"
                - "Festival Event"
                - "Leisure Activity"
                - "Accommodation"
                - "Shopping"
                - "Restaurant"
                - "Transportation"
            area_code (str, optional): Area code to filter results. Valid values:
                - "1" (Seoul)
                - "2" (Incheon)
                - "3" (Daejeon)
                - "4" (Daegu)
                - "5" (Gwangju)
                - "6" (Busan)
                - "7" (Ulsan)
                - "8" (Sejong)
                - "31" (Gyeonggi-do)
                - "32" (Gangwon-do)
                - "33" (Chungcheongbuk-do)
                - "34" (Chungcheongnam-do)
                - "35" (Gyeongsangbuk-do)
                - "36" (Gyeongsangnam-do)
                - "37" (Jeonbuk-do)
                - "38" (Jeollanam-do)
                - "39" (Jeju-do)
            language (str, optional): Language for results (default: "en"). Supported:
                - "en" (English)
                - "jp" (Japanese)
                - "zh-cn" (Simplified Chinese)
                - "zh-tw" (Traditional Chinese)
                - "de" (German)
                - "fr" (French)
                - "es" (Spanish)
                - "ru" (Russian)
            page (int, optional): Page number for pagination (default: 1, min: 1)
            rows (int, optional): Number of items per page (default: 20, max: 100)
            filter (list[str], optional): List of keys to include in each result item (whitelist).
                - If filter is None or an empty list ([]), all fields are returned.
                - If filter contains values, only the specified keys will be included in each item, and all other keys will be removed.
    
        Returns:
            dict: Search results with structure:
            {
                "total_count": int,     # Total number of matching items
                "num_of_rows": int,     # Number of items per page
                "page_no": int,         # Current page number
                "items": [              # List of tourism items
                    {
                        "title": str,           # Name of the attraction/place
                        "addr1": str,           # Primary address
                        "addr2": str,           # Secondary address
                        "areacode": str,        # Area code
                        "sigungucode": str,     # Sigungu code
                        "cat1": str,            # Category 1 code
                        "cat2": str,            # Category 2 code
                        "cat3": str,            # Category 3 code
                        "contentid": str,       # Unique content ID
                        "contenttypeid": str,   # Content type ID
                        "createdtime": str,     # Creation timestamp
                        "modifiedtime": str,    # Last modified timestamp
                        "tel": str,             # Phone number
                        "firstimage": str,      # URL of main image
                        "firstimage2": str,     # URL of thumbnail image
                        "mapx": str,            # Longitude
                        "mapy": str,            # Latitude
                        "mlevel": str,          # Map level
                        "cpyrhtDivCd": str      # Copyright division code
                    }
                    # ... more items
                ]
            }
    
        Example:
            search_tourism_by_keyword("Gyeongbokgung", "Tourist Attraction", "1", "en", 1, 10)
        """
        # Get the API client lazily
        client = get_api_client()
    
        # Validate and convert content_type
        content_type_id = None
        if content_type:
            content_type_id = next(
                (
                    k
                    for k, v in CONTENTTYPE_ID_MAP.items()
                    if v.lower() == content_type.lower()
                ),
                None,
            )
            if content_type_id is None:
                valid_types = ", ".join(CONTENTTYPE_ID_MAP.values())
                raise ValueError(
                    f"Invalid content_type: '{content_type}'. Valid types are: {valid_types}"
                )
    
        # Call the API client and return dict directly
        result = await client.search_by_keyword(
            keyword=keyword,
            content_type_id=content_type_id,
            area_code=area_code,
            language=language,
            page=page,
            rows=rows,
        )
        if filter:
            # Apply additional filtering if provided
            filter_items = []
            for item in result.get("items", []):
                item = {k: v for k, v in item.items() if k in filter}
                filter_items.append(item)
            result["items"] = filter_items
        return result
  • The registration of the search_tourism_by_keyword tool using the @mcp.tool decorator.
    @mcp.tool
    async def search_tourism_by_keyword(
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: pagination support, filtering by content type/area, language options, and whitelist filtering behavior. However, it doesn't mention rate limits, authentication requirements, or error conditions that would be helpful for a search tool.

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 well-structured with clear sections (description, args, returns, example). The front-loaded purpose statement is efficient, though the detailed parameter documentation is lengthy but necessary given the schema coverage gap.

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 7-parameter search tool with no annotations and 0% schema coverage, the description provides comprehensive documentation: clear purpose, detailed parameter semantics with examples and valid values, return structure documentation, and an example. This fully compensates for the lack of structured metadata.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation: clear examples for keyword, exhaustive valid value lists for content_type, area_code, and language, and specific behavior explanations for filter parameter. All 7 parameters are well-documented beyond what the bare schema provides.

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 description clearly states the specific action ('search for tourism information'), resource ('Korea Tourism Organization database'), and scope ('by keyword'). It distinguishes from siblings like 'get_tourism_by_area' (area-based) and 'search_festivals_by_date' (date-based).

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 for keyword-based tourism searches but provides no explicit guidance on when to use this versus alternatives like 'get_tourism_by_area' or 'search_festivals_by_date'. It mentions filtering capabilities but doesn't specify when to choose this tool over other search methods.

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/harimkang/mcp-korea-tourism-api'

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