Skip to main content
Glama

find_rank_location

Read-only

Find the place a keyword is searched from, as a person types it: a city, region, postcode or country name. Returns DataForSEO's own places with the locationCode that add_rank_keywords takes. The list does not hold every postcode of a country; a place that is not found can be tracked by coordinates instead ("lat,lng" as the query returns them normalised). bingExact false means Bing cannot be pointed at that place and would search the whole country.

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": {
      "country": "<country>",
      "query": "<query>"
    },
    "name": "find_rank_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for: "auckland", "1010", "hamburg" — or coordinates "lat,lng".
countryYesCountry, ISO 3166-1 alpha-2 (e.g. "nz", "de").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioural context beyond them: the dataset is DataForSEO's own place list and is incomplete for postcodes, and the bingExact flag signals whether Bing can target a place at all. It does not discuss result limits or ordering, but it discloses the main gotchas an agent would otherwise discover at runtime.

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, front-loaded with purpose, then the return value, then caveats. Everything earns its place, though the trailing Bing sentence reads as an appendix rather than integrated guidance.

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

Completeness5/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 does so ('DataForSEO's own places with the locationCode'), plus the two failure modes (missing postcodes, bingExact false). For a two-parameter read-only lookup with fully documented schema, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds matching semantics the schema lacks — the query is interpreted 'as a person types it' and coordinate strings are returned normalised. Country is only implicitly tied to ISO 3166-1 via the schema, but the added interpretation guidance is genuine value.

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?

Names a specific verb and resource ('Find the place a keyword is searched from') and immediately scopes it to a city, region, postcode or country. It also identifies its downstream consumer ('the locationCode that add_rank_keywords takes'), which separates it cleanly from the keyword-management siblings.

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?

Gives a clear context of use (resolving a location before adding rank keywords) and an explicit fallback path when lookup fails ('a place that is not found can be tracked by coordinates instead'). It stops short of naming an alternative sibling or stating exclusions, so it is clear but not exhaustive routing guidance.

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