Skip to main content
Glama
serper-live

Serper Live

by serper-live
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Domain position in Google

domain_position
Read-only

Checks where a domain ranks in Google organic results for a keyword, by country and device. Use it to track one site's position, returning the rank found or noting if it's outside the checked depth.

Instructions

Find where a domain ranks in Google's organic results for a keyword, in a country and on a device, right now. Prefer it over google_search when only one site matters: it returns that site's best position and every other position, or a note that the site is outside the checked depth. A subdomain counts as the domain: example.com also matches blog.example.com. Billed like google_search, per started 10 results of depth (https://serper.live/pricing).

Input Schema

NameRequiredDescriptionDefault
depthNoHow many organic results to check, 1–100. Default: 10. Use 30 or more to see positions beyond the first page.
queryYesSearch keyword, exactly as a person would type it into Google.
deviceNoBrowser persona Google sees. Desktop and mobile rankings often differ. Default: desktop.
domainYesDomain to look for, e.g. "example.com". Scheme, path and a leading www are ignored.
countryYesTwo-letter code of the market to search in, e.g. "US", "GB", "DE", "FR", "TR": Google sees a visitor from this country. Call list_countries for the markets that are open right now.
languageNoGoogle interface language (hl), e.g. "en", "de", "fr", "uk". Defaults to the language of the country; the market itself is set by country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter code of the market to search in, e.g. \"US\", \"GB\", \"DE\", \"TR\". Call list_countries for the markets that are open right now."New value: +"Two-letter code of the market to search in, e.g. \"US\", \"GB\", \"DE\", \"FR\", \"TR\": Google sees a visitor from this country. Call list_countries for the markets that are open right now."
    • changedInput schema / properties / language / description
      Previous value: -"Google interface language (hl), e.g. \"en\", \"de\", \"uk\". Defaults to the language of the country."New value: +"Google interface language (hl), e.g. \"en\", \"de\", \"fr\", \"uk\". Defaults to the language of the country; the market itself is set by country."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent=false, but the description adds real substance beyond them: billing model ('per started 10 results of depth' with a pricing link), the freshness claim ('right now'), and the subdomain-matching rule. It does not restate the return payload's structure in detail, so a 4 rather than 5.

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?

Four tight sentences with zero filler, front-loaded with purpose then the sibling comparison then the matching/billing caveats. Every sentence carries information an agent needs.

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?

No output schema exists, but the description compensates by describing the return content ('that site's best position and every other position, or a note that the site is outside the checked depth'). Combined with 100% schema coverage and annotations, an agent has everything needed to call it correctly.

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 baseline is 3; the description nevertheless adds a non-schema rule ('A subdomain counts as the domain: example.com also matches blog.example.com') that changes how the domain argument should be chosen.

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?

States a specific verb + resource + scope ('Find where a domain ranks in Google's organic results for a keyword, in a country and on a device, right now') and explicitly contrasts itself with the sibling google_search. An agent can select it without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit selection rule: 'Prefer it over google_search when only one site matters.' It also routes to list_countries for open markets via the country param description, covering the alternative-tool decision.

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

Deploy Server

Other Tools