{
"name": "searchapi_naver",
"description": "Naver Search results from SearchApi, as structured JSON.",
"input_schema": {
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "Search query; most engines accept native operators and advanced filters."
},
"where": {
"type": "string",
"description": "Naver vertical to search.",
"enum": [
"web",
"nexearch",
"news",
"blog",
"view",
"image"
]
},
"page": {
"type": "integer",
"description": "Page number of the results.",
"default": 1
}
},
"required": [
"q"
],
"examples": [
{
"q": "coffee"
}
]
}
}Paste the definition into your own agent's tools array. The schema is generated from this engine's catalog entry, and the reader's configured values ride in the schema's examples. The name is ours rather than the MCP server's — it is what your agent will call — and every engine's is prefixed searchapi_.