Skip to main content
Glama
leadbrain

korean-data-mcp

get_naver_place_reviews

Fetch customer reviews from a Naver Place listing by providing its URL. You can optionally set the maximum number of reviews to receive, up to 100.

Instructions

Fetch reviews for a Naver Place (네이버 플레이스) listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
place_urlYesNaver Place URL, e.g. https://map.naver.com/v5/entry/place/1234567890
max_reviewsNoMaximum number of reviews to return (default 20, max 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_naver_place_reviews async function is decorated with @mcp.tool(), making it an MCP tool. It accepts a place_url (str) and max_reviews (int, default 20, capped at 100), then delegates to the Apify helper _run_actor with actor ID 'oxygenated_quagmire/naver-place-reviews' and input {'placeUrl': place_url, 'maxReviews': max_reviews}. Returns a list of review dicts.
    @mcp.tool()
    async def get_naver_place_reviews(
        place_url: str,
        max_reviews: int = 20,
    ) -> list[dict]:
        """
        Fetch reviews for a Naver Place (네이버 플레이스) listing.
    
        Args:
            place_url: Naver Place URL, e.g. https://map.naver.com/v5/entry/place/1234567890
            max_reviews: Maximum number of reviews to return (default 20, max 100)
    
        Returns:
            List of review objects with author, rating, content, date fields.
        """
        max_reviews = min(max_reviews, 100)
        return await _run_actor(
            f"{APIFY_ACCOUNT}/naver-place-reviews",
            {"placeUrl": place_url, "maxReviews": max_reviews},
        )
  • The tool is registered via the FastMCP decorator @mcp.tool() on the get_naver_place_reviews function. No additional registration code is needed — FastMCP automatically discovers decorated functions.
    @mcp.tool()
    async def get_naver_place_reviews(
  • The _run_actor helper function is the underlying implementation that calls the Apify API. It constructs a URL with actor_id, sends input_data via POST, and returns the dataset items as a list of dicts. It is shared by all tools in the server.
    async def _run_actor(actor_id: str, input_data: dict, timeout_secs: int = 60) -> list[dict]:
        """Run an Apify actor synchronously and return dataset items."""
        token = _get_token()
        url = f"{APIFY_BASE}/acts/{actor_id}/run-sync-get-dataset-items"
        params = {"token": token}
    
        async with httpx.AsyncClient(timeout=timeout_secs + 10) as client:
            resp = await client.post(url, json=input_data, params=params)
            resp.raise_for_status()
            return resp.json()
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only says 'Fetch reviews' with no mention of authentication, rate limits, or side effects. The read-only nature is implied but not explicit, and no constraints are communicated.

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 a single sentence of 8 words, front-loaded with the core action. Every word earns its place, making it highly efficient and easy to parse. No verbose or redundant information.

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

Completeness3/5

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

With an output schema present, return values are covered elsewhere. However, the description lacks context on prerequisites (e.g. valid URL format) and any usage limitations. It is minimally adequate but could benefit from additional context like required authentication or scope.

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

Parameters3/5

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

Schema coverage is 100% with both parameters described in the input schema. The description adds no additional meaning beyond what the schema already provides. Baseline score of 3 is appropriate as the schema does the heavy lifting.

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 fetches reviews for a Naver Place, using a specific verb 'Fetch' and resource 'reviews for a Naver Place'. It effectively distinguishes from sibling tools which focus on other services like music charts or search for other platforms.

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?

The description provides clear context that the tool is for fetching Naver Place reviews, implying usage when reviews are needed. No exclusions or alternatives are explicitly stated, but the sibling tools are distinct enough that confusion is unlikely.

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/leadbrain/korean-data-mcp'

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