Skip to main content
Glama

Litescrape

by com.litescrape
OverviewDiscussionsAdmin

Google Search

google_search
Read-only

Fetch a first-party Google Search results page as JSON: organic_results plus whichever modules Google served (knowledge_graph, answer_box, ai_overview, ads, related_questions, related_searches, local_results, top_stories, inline_videos and more). Supports localization, verticals (news, videos, local, shopping, patents), date filters and site restriction. Free without an API key: 25 calls per network per day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query; required unless ludocid or kgmid is supplied
crNoCountry restrict such as countryUS|countryCA
glNoTwo-letter country for localization, e.g. "us"
hlNoLanguage code such as "en" or "en-GB"; default en
lrNoLanguage restrict such as lang_en|lang_fr
latNoLatitude; supply together with lon
lonNoLongitude; supply together with lat
numNoRequested result count, 1-10; Google may return fewer
tbmNoVertical: lcl local, vid videos, nws news, shop shopping, pts patents
tbsNoGoogle search-filter string, e.g. qdr:w for the past week
nfprNo1 disables spelling auto-correction
safeNoSafeSearch
uuleNoPre-encoded Google location token; conflicts with location
kgmidNoKnowledge Graph machine ID such as /m/0k8z
startNoResult offset for pagination
as_qdrNoDate range: d, w, m or y with an optional count, e.g. d7 for the past week
deviceNoLayout to request; default desktop
filterNo0 disables duplicate-content filtering
radiusNoRadius in meters around the location or coordinates
ludocidNoGoogle CID of a local entity, for a targeted lookup
locationNoNamed search origin such as "Austin, Texas"; conflicts with uule and lat/lon
fast_modeNotrue returns only organic_results (faster and smaller); skips AI Overview, Knowledge Graph, ads and every other module
as_sitesearchNoRestrict results to this hostname
google_domainNoGoogle domain such as google.co.uk; default google.com
result_groupsNoReturn only these top-level result groups, e.g. ["organic_results", "knowledge_graph"]; omit for the complete response. search_metadata is always kept

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / num / description
      Previous value: -"Requested result count, 1-100; Google may return fewer"New value: +"Requested result count, 1-10; Google may return fewer"
    • changedInput schema / properties / num / maximum
      Previous value: -100New value: +10
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value comes from the rate limit ('25 calls per network per day') and from clarifying that results include 'organic_results plus whichever modules Google served'. There is no contradiction with annotations.

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?

The description is two sentences, front-loaded with the core purpose, and includes a valuable constraint ('Free without an API key: 25 calls per network per day') without redundancy. Every clause earns its place.

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 25 parameters and no output schema, the description adequately covers the return shape ('organic_results plus whichever modules Google served') and key constraints. It does not enumerate every module or required-parameter nuance, but the schema fills most gaps.

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 description coverage is 100%, so the baseline is 3. The description only summarizes capabilities like localization and verticals, without adding meaning beyond what the schema's per-parameter descriptions already provide.

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?

The description states a precise verb and resource: 'Fetch a first-party Google Search results page as JSON'. It also enumerates the returned modules and capabilities, making it easy to distinguish from sibling tools like bing_search or duckduckgo_search.

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

Usage Guidelines3/5

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

The description gives clear context by listing supported localizations, verticals, date filters, and site restrictions, but it never explicitly says when to choose this tool over its siblings or when to avoid it. Usage is implied rather than stated.

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

All Litescrape toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources