Skip to main content
Glama
serper-live

Serper Live

by serper-live
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Live Google search

google_search
Read-only

Search Google by country, language, and device to retrieve organic results in rank order, including position, title, URL, domain, and snippet. Use it to review the full result list.

Instructions

Run a live Google search for a country, language and device and return the organic results in Google's order: position, title, URL, domain and snippet. Ads, sitelinks, video and image blocks are left out, so position is the organic rank. Every call is a real, uncached search that usually takes 2–3 seconds and is billed to the Serper.live balance per page of up to 10 results (https://serper.live/pricing). Use it to see the whole result list; to check where one site ranks, use domain_position instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many organic results to return, 1–100. Default: 10. Each started page of 10 results is billed.
queryYesSearch keyword, exactly as a person would type it into Google.
deviceNoBrowser persona Google sees. Desktop and mobile rankings often differ. Default: desktop.
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.6/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly, openWorld, non-idempotent), and the description layers on real operational traits: uncached live search, 2–3 second latency, per-page billing against the Serper.live balance with a pricing link. It also discloses result exclusions (ads, sitelinks, video, image blocks) so the meaning of 'position' is unambiguous.

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?

Front-loaded with the core action, then return shape, then cost/latency, then routing advice. Every sentence carries information, though the billing mechanics (per page of 10) are stated twice across description and schema limit field.

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, and the description compensates by naming the returned fields (position, title, URL, domain, snippet). Combined with cost, latency, exclusions and the sibling routing, nothing an agent needs to call this correctly 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?

With 100% schema description coverage, the schema already documents query, country, language, device and limit in detail, including defaults and billing notes. The description adds only reinforcing context ('Google sees a visitor from this country'), so the baseline of 3 is appropriate.

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 (run a live Google search) and resource (organic results), and enumerates the returned fields in Google's order. It explicitly carves itself out from domain_position (whole result list vs. one site's rank), so an agent can select correctly without opening a 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?

Names the alternative tool and the condition that selects it: 'Use it to see the whole result list; to check where one site ranks, use domain_position instead.' It also routes the agent to list_countries for valid market codes, covering both the when-to-use and the dependency case.

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