Skip to main content
Glama
eMCP for Evolution CMS

eMCP for Evolution CMS

Official

Serp Tool

adataforseo.serp

Retrieves a target page's last checked Google top 10 results and difficulty score, helping assess search competition and prioritize SEO work.

Instructions

Read-only. One target page with its last checked Google top 10 (host, title, strength) and difficulty.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "adataforseo.serp"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesTarget id from adataforseo.matrix

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations are empty, so the description carries the full behavioral burden. It does useful work by self-declaring 'Read-only' and flagging that the data is 'last checked' rather than live, which warns the agent about staleness. It says nothing about refresh triggers, permission requirements, or behavior when a target has no recorded SERP history.

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?

Two short clauses with the safety signal ('Read-only') front-loaded, then the return shape. Nothing is padded or repeated. Minor cost: 'strength' and 'difficulty' are unexplained jargon, though that is a completeness rather than verbosity issue.

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?

For a simple one-parameter read tool with no output schema, the description covers the essential return fields, which is the right level of effort. However, with no annotations and no output schema, it should clarify what 'strength'/'difficulty' represent and how 'last checked' is determined, so an agent knows whether the data is current enough for its task.

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 coverage is 100% and the single parameter is already documented as 'Target id from adataforseo.matrix'. The description adds only the framing that this target corresponds to one page, adding no new syntax, range, or sourcing detail. Baseline 3 is appropriate for a fully documented single parameter.

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 names the resource precisely: the last checked Google top 10 for a single target page, with the returned fields (host, title, strength) plus difficulty. This lets an agent distinguish it from portfolio-level siblings like adataforseo.matrix or adataforseo.rankings. It lacks an explicit verb ('Get'/'Fetch'), but the read-only noun phrase is unambiguous.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'One target page' only weakly implies that broader or multi-target views belong elsewhere, and no sibling is named or excluded. An agent must infer the selection criteria from the word 'One' alone.

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