Skip to main content
Glama

Google Search Light

google_search_light
Read-only

Perform fast Google web searches. Returns organic search results, related searches, and pagination. Suitable for quick information retrieval when advanced filtering is not needed. Requires a search query in q. A result whose link is a Google redirect carries a token beside it: if google_resolve is among your tools, pass the token to it for the destination URL.

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": {
      "q": "<q>"
    },
    "name": "google_search_light"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query. The parameter is named 'q' (not 'query'). Required.
glNoCountry code for search context (e.g., 'us', 'gb'). Default: us.
numNoNumber of results per page (1-10). Default: 10.
pageNoPage number for pagination. Default: 1.
safeNoSafeSearch filtering level. Default: blur.
latitudeNoLatitude of the search location, in decimal degrees (-90 to 90). Use with `longitude`.
longitudeNoLongitude of the search location, in decimal degrees (-180 to 180). Use with `latitude`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / latitude
      Added value: +{
      +  "description": "Latitude of the search location, in decimal degrees (-90 to 90). Use with `longitude`.",
      +  "type": "number"
      +}
    • addedInput schema / properties / longitude
      Added value: +{
      +  "description": "Longitude of the search location, in decimal degrees (-180 to 180). Use with `latitude`.",
      +  "type": "number"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Search query. Required."New value: +"Search query. The parameter is named 'q' (not 'query'). Required."
  3. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed2 schema fields changed
    • changedInput schema / properties / safe / description
      Previous value: -"Safe search setting. 'active' filters explicit content."New value: +"SafeSearch filtering level. Default: blur."
    • changedInput schema / properties / safe / enum
      Previous value: -[
      -  "active",
      -  "off"
      -]New value: +[
      +  "active",
      +  "blur",
      +  "off"
      +]
  5. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-idempotent/non-destructive, so the safety profile is covered. The description adds real value on top: it discloses the shape of the response (organic results, related searches, pagination) and the redirect-token handoff behavior, which an agent could not infer from the schema. Return format detail is thin (no field names, no total-count semantics), so not a 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?

Four compact sentences, front-loaded with purpose and return contents, then usage, then the edge-case rule. Minor waste in restating the `q` requirement already documented in the schema, but no padding or hedging.

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 7 parameters, no output schema, and annotations covering safety, the description supplies enough to call it correctly: what it returns, how pagination works, and how to handle redirect links. It does not discuss rate limits, result-set size limits, or failure modes, leaving a small gap.

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 every parameter already carries its own description including defaults and ranges, so the description only restates that `q` is required and named 'q' not 'query'. No added semantics for gl, num, page, safe, or the latitude/longitude pairing. Baseline 3 applies.

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?

States a specific verb and resource (fast Google web searches) and enumerates what comes back: organic results, related searches, pagination. It implicitly differentiates itself from heavier search variants via 'when advanced filtering is not needed', though it never names a concrete sibling (duckduckgo_search_light, google_scholar, google_ai_mode) to sharpen the contrast.

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 usable selection criterion ('quick information retrieval when advanced filtering is not needed') and a concrete routing rule: if a result link is a Google redirect and google_resolve is available, pass the token to it. No explicit when-not exclusions naming an alternative tool, which keeps it from 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