Skip to main content
Glama

Seo Serp

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Seo Serp Google

seo_serp_google
Read-onlyIdempotent

Who ranks for <term> on Google — live organic search results (rank, title, domain, URL, snippet) for a keyword in a given country. SEO rank-tracking and SERP analysis. Example: seo_serp_google({ keyword: "best running shoes", location_code: 2840, _apiKey: "your-base64-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNoNumber of organic results to return (default 10, max 20)
_apiKeyYesDataForSEO API key = base64("login:password") from your dataforseo.com account
keywordYesSearch query to look up, e.g. "best running shoes"
language_codeNoTwo-letter language code (default "en")
location_codeNoDataForSEO location code (default 2840 = United States). e.g. 2826 = UK, 2124 = Canada.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "_apiKey": "your-seo-serp-api-key",
-    "depth": 10,
-    "keyword": "best running shoes",
-    "language_code": "en",
-    "location_code": 2840
-  },
-  {
-    "_apiKey": "your-seo-serp-api-key",
-    "keyword": "machine learning courses",
-    "location_code": 2826
-  }
-]New value: +[
+  {
+    "depth": 10,
+    "keyword": "best running shoes",
+    "language_code": "en",
+    "location_code": 2840
+  },
+  {
+    "keyword": "machine learning courses",
+    "location_code": 2826
+  }
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-seo-serp-api-key",
+    "depth": 10,
+    "keyword": "best running shoes",
+    "language_code": "en",
+    "location_code": 2840
+  },
+  {
+    "_apiKey": "your-seo-serp-api-key",
+    "keyword": "machine learning courses",
+    "location_code": 2826
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable context beyond those annotations: results are live, organic, and location-scoped, and it enumerates the returned fields. It omits potential rate-limit or failure behavior, but that is secondary given the annotation coverage.

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

Conciseness5/5

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

The description is compact, front-loaded with the core value proposition, and includes a useful invocation example. Every part earns its place and there is no filler.

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

Completeness4/5

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

With no output schema present, the description compensates by specifying the exact result fields expected. The schema covers parameter defaults and API key requirements, so an agent has enough information to invoke the tool correctly. Minor additional details like result count limits are already in the schema, so nothing important is missing.

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 100%, with all five parameters documented including defaults such as location_code 2840 and depth max 20. The description's example reinforces the usage of keyword, location_code, and _apiKey but does not add semantic meaning beyond what the schema already provides.

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

Purpose5/5

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

The description names a specific resource (Google organic search results) and a precise deliverable: rank, title, domain, URL, and snippet for a keyword in a country. This is clearly distinct from the unrelated sibling tools and leaves no ambiguity about what the tool does.

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

Usage Guidelines3/5

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

The phrase 'SEO rank-tracking and SERP analysis' plus a concrete example communicates the intended context. However, it does not explicitly state when to prefer this tool over alternatives or any exclusion criteria, though no close sibling exists in the provided list.

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

All Seo Serp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources