Skip to main content
Glama

AIsa SERP — Other Engines

by one.aisa
OverviewDiscussionsAdmin

Setting Naver Organic SERP Tasks

post_dataforseo_serp_naver_organic_submit
Destructive

Naver SERP API provides top 15 search engine results. Naver search results do not vary by location and language, and the search parameters for this search engine do not contain language and location variables. However, you can specify a keyword in any language, and the search engine results may vary depending on the language you used for specifying the search query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / body / items / properties / depth / description
      Previous value: -"Parsing depth"New value: +"parsing depth optional field number of results in SERP default value: 15 max value: 700 Your account will be billed per each SERP containing up to 15 results; Setting depth above 15 may result in additional charges if the search engine returns more than 15 results; The cost can be calculated on the Pricing page."
    • changedInput schema / properties / body / items / properties / device / description
      Previous value: -"Device type"New value: +"device type optional field return results for a specific device type can take the values:desktop, mobile default value: desktop"
    • changedInput schema / properties / body / items / properties / keyword / description
      Previous value: -"Keyword to search for"New value: +"keyword required field you can specify up to 700 characters in the keyword field all %## will be decoded (plus character ‘+’ will be decoded to a space character) if you need to use the “%” character for your keyword, please specify it as “%25”; if you need to use the “+” character for your keyword, please specify it as “%2B” learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article"
    • changedInput schema / properties / body / items / properties / os / description
      Previous value: -"Device operating system"New value: +"device operating system optional field if you specify desktop in the device field, choose from the following values: windows, macos default value: windows if you specify mobile in the device field, choose from the following values: android, ios default value: android"
    • changedInput schema / properties / body / items / properties / pingback_url / description
      Previous value: -"Notification URL of a completed task"New value: +"notification URL of a completed task optional field when a task is completed we will notify you by GET request sent to the URL you have specified you can use the ‘$id’ string as a $id variable and ‘$tag’ as urlencoded $tag variable. We will set the necessary values before sending the request. example: http://your-server.com/pingscript?id=$id http://your-server.com/pingscript?id=$id&tag=$tag Note: special characters in pingback_url will be urlencoded; i.a., the # character will be encoded into %23 learn more on our Help Center"
    • changedInput schema / properties / body / items / properties / postback_data / description
      Previous value: -"Postback datatype; possible values: regular, advanced, html"New value: +"postback_url datatype required field if you specify postback_url corresponds to the function you used for setting a task possible values: regular, advanced, html"
    • changedInput schema / properties / body / items / properties / postback_url / description
      Previous value: -"URL for sending task results"New value: +"URL for sending task results optional field once the task is completed, we will send a POST request with its results compressed in the gzip format to the postback_url you specified you can use the ‘$id’ string as a $id variable and ‘$tag’ as urlencoded $tag variable. We will set the necessary values before sending the request. example: http://your-server.com/postbackscript?id=$id http://your-server.com/postbackscript?id=$id&tag=$tag Note: special characters in postback_url will be urlencoded; i.a., the # character will be encoded into %23 learn more on our Help Center"
    • changedInput schema / properties / body / items / properties / priority / description
      Previous value: -"Task priority"New value: +"task priority optional field can take the following values: 1 – normal execution priority (set by default) 2 – high execution priorityYou will be additionally charged for the tasks with high execution priority. The cost can be calculated on the Pricing page."
  2. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=true, openWorld=true, idempotent=false, so the mutation profile is covered. The description adds genuinely beyond that by explaining that Naver results do not vary by location or language, which affects expectations about the optional fields; however it omits the asynchronous task flow (submission returns a task id later fetched) that defines a 'submit' tool.

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?

Three sentences, no filler, and the engine-behavior constraints are stated plainly up front. Reasonably sized for the amount of context it chooses to give.

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?

An output schema exists, so return values need not be explained, and the annotations carry the safety profile. What is missing is the submit-task pattern (async creation, pairing with fetch/get_details tools) and any description of the required body structure, which leaves the definition incomplete for an unfamiliar agent.

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?

The description usefully clarifies that location and language variables do not affect Naver results, implicitly telling the agent that location_code/location_name/language_code/language_name need not be set. It also notes the keyword can be in any language. But the top-level 'body' array parameter (the sole required param, 0% description coverage) is not described at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description talks about what the Naver SERP API is ('provides top 15 search engine results') rather than stating what this tool does. It never uses a verb like 'submit', 'create', or 'queue a task', even though the name and title say 'submit'/'Setting Tasks'. An agent learns about Naver's behavior but not the tool's action.

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?

There is no guidance on when to use this submission tool versus the sibling fetch tools (get_dataforseo_serp_naver_organic_fetch, _fetch_html, _fetch_regular) or other engines' submit tools. The note about location/language not applying is a fact about the engine, not a use/exclusion rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AIsa SERP — Other Engines toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources