Skip to main content
Glama
artgas1

xmlriver-mcp

by artgas1

google_search

Read-onlyIdempotent

Parse Google search results for SEO research, keyword discovery, and SERP feature analysis. Retrieve organic listings, featured snippets, and knowledge graph data for any query and locale.

Instructions

Parse Google search results page (SERP) for a given query and locale.

Use this for: SEO research (own/competitor ranking), keyword discovery, SERP feature analysis (featured snippets, knowledge graph, FAQ), competitive intel.

Do NOT use for: live page content fetching (use a dedicated scraper for that), Google Ads keyword planner data (use Yandex Wordstat via wordstat_query for RU).

Returns: Dict with: - query (echoed) - total_found — Google's reported result count - page — page number - results — list of organic results with position, url, title, snippet - addresults — featured_snippet, related_questions, related_searches, knowledge_graph (if present and requested via additional_blocks) - Or isError: True on XMLRiver error (15 = no results, 110 = rate limit, etc).

Examples: google_search(query="python tutorial", country=2008, language="ru") → {"results": [...10 organic results...], "total_found": 12300, "page": 1}

google_search(query="site:wikipedia.org python", country=2840, language="en")
→ results restricted to wikipedia.org domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query. Plain text or with Google operators (site:, inurl:, etc). Example: 'купить iphone 15' or 'site:wikipedia.org openai'.
countryNoCountry ID for Google location. Default 2008 (Russia). Common values: 2008=RU, 2840=US, 2826=UK, 2276=DE, 2250=FR, 2724=ES, 2484=MX. Full list: https://xmlriver.com/apidoc/country/
domainNoGoogle domain ID. Default 10 (google.com). Common: 10=google.com, 11=google.co.uk, 53=google.com.tr, 84=google.ru. Full list: https://xmlriver.com/apidoc/domain/
languageNoInterface language code (Google `lr` param). Examples: 'ru' (Russian), 'en' (English), 'de' (German), 'es' (Spanish). Default 'ru'.ru
deviceNoDevice emulation. Default 'desktop'.desktop
pageNoPage number (1-based). Default 1.
locationNoOptional precise location ID (Google `loc` param). Overrides country/region with city-level precision. Full list: https://xmlriver.com/apidoc/loc/
date_filterNoDate filter (Google `tbs` param). Examples: 'qdr:h' (last hour), 'qdr:d' (24h), 'qdr:w' (week), 'qdr:m' (month), 'qdr:y' (year), or custom 'cdr:1,cd_min:1/1/2024,cd_max:6/1/2024'.
additional_blocksNoComma-separated extra blocks to parse: 'topads,bottomads,faqsnippet,rq,rs,knowledge_graph,sitelinks,g_news,g_videos,g_inlineshopping,searchsters,scroller,extended_snippet'. Each adds parsing cost on XMLRiver side but no extra charge.
ai_overviewNoParse Google's AI Overview block (slower, costs extra). Default False.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive. Description adds valuable behavioral detail: error codes (15=no results, 110=rate limit), cost implications of AI Overview and additional_blocks, and output structure. No contradiction.

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?

Well-structured with sections (purpose, use cases, returns, examples). No redundant sentences; each part earns its place. Front-loaded with clear purpose.

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?

Given 10 parameters, output schema details, and error handling, the description covers everything needed. Examples demonstrate typical and advanced usage. No gaps identified.

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 already describes all 10 parameters well (100% coverage). Description goes beyond with examples, common values for country/domain, and clarifies behavior (e.g., additional_blocks adds parsing cost but no extra charge). Adds significant value, justifying above baseline.

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 explicitly states verb+resource ('Parse Google search results page') and lists specific use cases (SEO research, keyword discovery, SERP feature analysis). It distinguishes from sibling tools like yandex_search and wordstat_query via the 'Do NOT use' section.

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?

Clear 'Use this for' and 'Do NOT use for' sections with explicit alternatives (e.g., 'use Yandex Wordstat via wordstat_query for RU'). Covers both positive and negative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/artgas1/xmlriver-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server