Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Search SERP locations

seo_search_serp_locations
Read-onlyIdempotent

Find the exact DataForSEO location name of a city, county, or region. Returns up to 50 matches; pass the chosen locationName verbatim to seo.create_rank_tracker for local rank tracking, or to seo.research_keywords for local search volume. Uses no credits. It calls one fixed endpoint of the Sextant SEO API (https://sextantweb.com/docs/ai): query is search text.

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": {
      "siteId": "<siteId>",
      "query": "<query>",
      "countryCode": "<countryCode>"
    },
    "name": "seo_search_serp_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPlace name, e.g. "Catonsville" or "Portland OR".
siteIdYesThe Sextant site ID.
countryCodeYesTwo-letter ISO country code, e.g. "us".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive safety traits, and the description goes beyond them by disclosing the 50-match result cap and 'Uses no credits', which the annotations do not convey. It also states it hits one fixed Sextant SEO API endpoint, which is useful scope information. It does not explain match ordering or what happens on zero matches, keeping it below 5.

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?

The core purpose and the downstream routing are front-loaded and efficient. The trailing 'It calls one fixed endpoint of the Sextant SEO API (https://sextantweb.com/docs/ai): query is search text.' is somewhat bolted on and partially redundant, which costs a point.

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, the description carries the burden of explaining returns, and it does so at a high level ('up to 50 matches' of location names) plus how to consume them. Given a simple 3-parameter read tool fully covered by schema, this is nearly complete; only the shape of each match is left implicit.

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%, so all three parameters are documented in the schema (query as place name with examples, siteId, ISO countryCode with a regex pattern). The description adds only the trailing 'query is search text', which restates the schema; siteId and countryCode receive no added meaning.

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 opens with a specific verb and resource: 'Find the exact DataForSEO location name of a city, county, or region.' It names the entity returned (location name), scopes it to place types, and no sibling tool in the catalog performs this lookup, so the agent can distinguish it without ambiguity.

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

Usage Guidelines4/5

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

It gives clear downstream context — 'pass the chosen `locationName` verbatim to seo.create_rank_tracker for local rank tracking, or to seo.research_keywords for local search volume' — telling the agent exactly why it would call this. It stops short of stating exclusion conditions (e.g., when not to resolve a location, or what to do when no match is found), so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources