Skip to main content
Glama

Searchapi

by io.searchapi
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no need to repeat. The description adds value by specifying return contents (organic results, related searches, pagination) and the 'fast' nature, which are not covered by annotations. No contradictions.

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?

Two sentences with zero fluff. Purpose, return summary, and usage condition are front-loaded and each sentence earns its place. Perfectly concise for the information conveyed.

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?

For a read-only search tool with full schema coverage and no output schema, the description gives a high-level return summary and usage context. It does not detail the output structure, but given the simplicity and annotations covering safety, it is sufficiently complete. Could mention rate limits or output format, but not critical.

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%, so all parameters are already documented in the input schema. The description only reinforces the requirement for 'q' and does not add extra semantic meaning beyond what the schema provides. Baseline 3 applies because the schema does the heavy lifting.

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 ('Perform fast Google web searches') and clarifies what is returned (organic results, related searches, pagination). The name 'light' and mention of 'advanced filtering not needed' help differentiate from more specialized search siblings like google_scholar or google_images_light, even without naming them explicitly.

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?

Provides a clear usage condition: 'Suitable for quick information retrieval when advanced filtering is not needed.' This implies when to use it, but it does not explicitly name alternatives or exclusions. It also notes the required parameter, adding practical guidance. Slightly better than average but lacks explicit routing to siblings.

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

All Searchapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources