Skip to main content
Glama
jikime

Naver Search MCP Server

search_image

Search for images using keywords with options to filter by size, sort by relevance or date, and navigate through result pages.

Instructions

Searches for images using the given keyword. The page parameter allows for page navigation and sort='sim'/'date', filter='all'/'large'/'medium'/'small' is supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
displayNo
pageNo
sortNosim
filterNoall

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The asynchronous handler function that executes the core logic of the 'search_image' tool by preparing parameters and calling the image search API endpoint.
    async def search_image(query: str, display: int = 10, page: int = 1, sort: str = "sim", filter: str = "all") -> str:
        """
        Searches for images using the given keyword. The page parameter allows for page navigation and sort='sim'/'date', filter='all'/'large'/'medium'/'small' is supported.
    
        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).
            filter (str, optional): The image size filter. Default is "all" (all sizes).
        """
        start = calculate_start(page, display)
        display = min(display, 100)
        params = {"query": query, "display": display, "start": start, "sort": sort, "filter": filter}
        return await _make_api_call("image.json", params, ImageResult, "Image")
  • server.py:567-571 (registration)
    The @mcp.tool decorator registration that defines the tool name, description, and implicitly the input schema via the function signature.
    # 12. 이미지 검색
    @mcp.tool(
      name="search_image",
      description="Searches for images using the given keyword. The page parameter allows for page navigation and sort='sim'/'date', filter='all'/'large'/'medium'/'small' is supported."
    )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination and sorting/filtering options, which adds some context, but fails to cover critical aspects like rate limits, authentication needs, error handling, or what the search results entail (e.g., format, source). For a search tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 with two sentences that are front-loaded (starting with the core purpose) and avoid unnecessary fluff. Each sentence adds useful information about functionality and parameters, making it efficient, though it could be slightly more structured for clarity.

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 (5 parameters, no annotations, but with an output schema), the description is partially complete. It covers the basic purpose and some parameter details, but lacks usage guidelines and full behavioral context. The presence of an output schema mitigates the need to explain return values, but overall, it's adequate with clear gaps for a search tool.

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 description coverage is 0%, so the description must compensate. It adds value by explaining that 'page' allows for navigation and listing valid values for 'sort' and 'filter' (e.g., sort='sim'/'date', filter='all'/'large'/'medium'/'small'), which clarifies beyond the bare schema. However, it doesn't cover 'query' or 'display' parameters, leaving 2 of 5 parameters without semantic context, resulting in partial compensation.

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 tool's purpose as 'Searches for images using the given keyword,' which is a specific verb+resource combination. It distinguishes from most siblings (e.g., search_blog, search_news) by specifying 'images,' though it doesn't explicitly differentiate from all possible image-related tools that might exist elsewhere.

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. It mentions parameters like sort and filter but doesn't indicate scenarios where this tool is preferred over other search tools (e.g., search_webkr for web content) or when not to use it, leaving the agent without contextual usage cues.

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