Skip to main content
Glama
harimkang

Korea Tourism API MCP Server

get_tourism_images

Retrieve images for Korean tourism items using content IDs. Provides original and thumbnail URLs with metadata in multiple languages for travel planning and content creation.

Instructions

Get images for a specific tourism item in Korea.

This tool retrieves all available images for a specific tourism item by its content ID. It provides both original and thumbnail image URLs along with image metadata.

Args: content_id (str): Content ID of the tourism item (obtained from other search functions) 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)

Returns: dict: Images with structure: { "total_count": int, # Total number of matching items "content_id": str, # Content ID this image belongs to "items": [ # List of image items { "contentid": str, # Content ID this image belongs to "imgname": str, # Image name "originimgurl": str, # URL of original image "smallimageurl": str, # URL of small/thumbnail image "serialnum": str, # Serial number "cpyrhtDivCd": str # Copyright division code } # ... more items ] }

Example: get_tourism_images("126508", "en", 1, 10)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_idYes
languageNo
pageNo
rowsNo

Implementation Reference

  • The implementation of the get_tourism_images tool handler.
    async def get_tourism_images(
        content_id: str,
        language: str | None = None,
        page: int = 1,
        rows: int = 20,
    ) -> dict:
        """
        Get images for a specific tourism item in Korea.
    
        This tool retrieves all available images for a specific tourism item by its
        content ID. It provides both original and thumbnail image URLs along with
        image metadata.
    
        Args:
            content_id (str): Content ID of the tourism item (obtained from other search functions)
            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)
    
        Returns:
            dict: Images with structure:
            {
                "total_count": int,     # Total number of matching items
                "content_id": str,      # Content ID this image belongs to
                "items": [              # List of image items
                    {
                        "contentid": str,       # Content ID this image belongs to
                        "imgname": str,         # Image name
                        "originimgurl": str,    # URL of original image
                        "smallimageurl": str,   # URL of small/thumbnail image
                        "serialnum": str,       # Serial number
                        "cpyrhtDivCd": str      # Copyright division code
                    }
                    # ... more items
                ]
            }
    
        Example:
            get_tourism_images("126508", "en", 1, 10)
        """
        # Call the API client and return dict directly
        results = await get_api_client().get_detail_images(
            content_id=content_id, language=language, page=page, rows=rows
        )
        # Add content_id to the results
        return {**results, "content_id": content_id}
  • Registration of the get_tourism_images tool using the @mcp.tool decorator.
    @mcp.tool
    async def get_tourism_images(
Behavior3/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 that the tool retrieves 'all available images' and provides both original and thumbnail URLs with metadata, which is helpful. However, it doesn't mention rate limits, authentication requirements, pagination behavior beyond parameters, or error conditions. The behavioral disclosure is adequate but incomplete.

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 well-structured with clear sections (purpose, args, returns, example) and front-loaded key information. While comprehensive, some sentences could be more concise (e.g., the language list could be streamlined). Overall, it's efficiently organized with minimal waste.

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

Completeness4/5

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

Given the tool's moderate complexity (4 parameters, no output schema, no annotations), the description provides good coverage. It explains parameters thoroughly, documents the return structure, and includes an example. The main gap is lack of behavioral context like rate limits or error handling, but overall it's quite complete for this tool type.

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. It explains content_id origin ('obtained from other search functions'), lists all supported language values with defaults, and specifies pagination behavior (defaults, min/max values). This adds substantial meaning beyond the bare schema.

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 tool's purpose: 'Get images for a specific tourism item in Korea' with specific verb ('retrieves') and resource ('images for a specific tourism item'). It distinguishes from siblings like 'get_detailed_information' or 'search_tourism_by_keyword' by focusing exclusively on image retrieval.

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 context through the parameter documentation (content_id 'obtained from other search functions'), suggesting this tool follows search operations. However, it doesn't explicitly state when to use this tool versus alternatives or provide clear exclusions. The guidance is functional but not comprehensive.

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