Skip to main content
Glama
jikime

Naver Search MCP Server

search_book

Search for book information on Naver using keywords, with options to navigate pages and customize display settings for targeted results.

Instructions

Searches for book information on Naver using the given keyword. The page parameter allows for page navigation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
displayNo
pageNo
sortNosim

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The async handler function that implements the core logic for the 'search_book' tool by calculating pagination parameters and calling the shared _make_api_call helper to query the Naver book search API.
    async def search_book(query: str, display: int = 10, page: int = 1, sort: str = "sim") -> str:
        """
        Searches for book information on Naver using the given keyword. The page parameter allows for page navigation.
    
        Args:
            query (str): The keyword to search for
            display (int, optional): The number of results to display. Default is 10.
            page (int, optional): The starting page number. Default is 1.
            sort (str, optional): The sorting criteria. Default is "sim" (similarity).
        """
        start = calculate_start(page, display)
        display = min(display, 100)
        params = {"query": query, "display": display, "start": start, "sort": sort}
        return await _make_api_call("book.json", params, BookResult, "Book")
  • server.py:399-402 (registration)
    MCP tool registration decorator that binds the search_book handler function to the tool name 'search_book'.
    @mcp.tool(
      name="search_book",
      description="Searches for book information on Naver using the given keyword. The page parameter allows for page navigation."
    )
  • Pydantic schema/model defining the fields for individual book items returned from the Naver book search API.
    class BookItem(BaseItem):
        image: Optional[str] = None
        author: Optional[str] = None
        price: Optional[str] = None
        discount: Optional[str] = None
        publisher: Optional[str] = None
        pubdate: Optional[str] = None
        isbn: Optional[str] = None
        description: Optional[str] = None
  • Pydantic schema/model for the complete book search response, inheriting from SearchResultBase and specifying items as List[BookItem]. Used for input validation and parsing in _make_api_call.
    class BookResult(SearchResultBase): items: List[BookItem]
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions page navigation but doesn't cover rate limits, authentication needs, error handling, or what the search returns beyond 'book information'. This is inadequate for a search tool with 4 parameters.

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 brief with two sentences. The first sentence states the core purpose, and the second adds parameter context. However, the second sentence could be more informative about other parameters.

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?

Given the tool's moderate complexity (4 parameters, no annotations, but has output schema), the description is minimally adequate. The output schema reduces the need to describe return values, but the description lacks crucial context about search scope, limitations, and parameter semantics.

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?

Schema description coverage is 0%, so the description must compensate but only adds meaning for the 'page' parameter. It doesn't explain 'query' (search keyword), 'display' (results per page), or 'sort' (ordering criteria), leaving 3 of 4 parameters semantically unclear.

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 action ('searches for book information') and target resource ('on Naver'), distinguishing it from siblings like search_blog or search_news. However, it doesn't explicitly differentiate from search_webkr or other search tools, keeping it at 4 rather than 5.

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 like search_webkr or search_doc. It mentions page navigation but offers no context about appropriate use cases or exclusions.

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/jikime/py-mcp-naver-search'

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