Skip to main content
Glama
Skobyn

SEO Tools MCP Server

serp_google_organic_task_post

Submit Google organic search results tasks to analyze keyword rankings across locations, languages, and devices for comprehensive SEO performance monitoring.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNoMaximum number of results to return
deviceNoThe device type for the search
keywordYesThe search query or keyword
language_codeYesThe language code for the search
location_codeYesThe location code for the search
osNoThe operating system for the search
postback_dataNoCustom data to be passed in the callback
postback_urlNoURL to receive a callback when the task is completed
priorityNoTask priority: 1 (normal) or 2 (high)
se_domainNoSearch engine domain (e.g., google.com)
tagNoCustom identifier for the task
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/Skobyn/dataforseo-mcp-server'

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