OpenSERP Cloudofficial
A
licenseB
qualityC
maintenanceSearch API for AI, SEO & automation. Browser-rendered Google, Bing, Yandex, Baidu, DuckDuckGo and Ecosia results with URL extraction (+image search and engine metadata tools)
9
87
2
MIT
serp-data-scraper
by com.jojapi
Server Details
SERP data scraper: Scrape Search Results and get all the data you need. On the JoJ API marketplace.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.9/5.0
Tool DescriptionsA
Average 3.8/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possible confusion between tools. The tool's purpose is clearly defined and singular.
Naming Consistency5/5
The single tool uses a clear snake_case verb_noun pattern ('post_serp'), which is consistent and descriptive. With only one tool, there is no inconsistency to evaluate.
Tool Count3/5
A single tool feels thin for most servers, but for a focused SERP scraping service it may be acceptable. Still, it borders on minimal, lacking any companion utilities or variations.
Completeness4/5
The tool fully covers the core purpose of scraping and parsing Google SERPs, including ads and organic results. However, it lacks features like pagination, multiple search engines, or result history, which are reasonable gaps for this scope.
Available Tools
1 toolpost_serpSERPAInspect
The Google SERP Parsing API allows you to extract structured data from Google Search Engine Results Pages (SERPs) with ease. It parses both ads and organic search results, returning a clean and organized JSON response. This is useful for SEO analysis, competitor research, monitoring search rankings, and more. Billing per call: 1 Credits.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | No | ||
| results_show | No | Minimum 100, maximum 500 | |
| proxy_country | No | One of: DE, US, GB, FR, AU, PL, JP, TW. If no country is selected, service will use random proxy. |
Tool Definition Quality
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description at least discloses that the tool returns clean JSON and costs 1 credit per call. It does not mention authentication, rate limits, side effects, or behavior when no keyword or proxy country is supplied.
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?
The description is concise and front-loaded with the main purpose, followed by useful context and cost information. Minor marketing filler like 'with ease' and 'and more' prevents a perfect score.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description is sufficient for an agent to understand what the tool does and roughly what it returns. It is not fully complete, though, because it lacks output schema / example response, exact required parameter behavior, and edge-case or error details.
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?
The schema provides meaningful descriptions for proxy_country and results_show, but keyword only has an example and no description. The description itself adds no parameter-specific insight, though the parameter names are mostly self-explanatory.
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 clearly states a specific verb and resource: it extracts structured data from Google SERPs and parses both ads and organic results. This makes the tool's purpose unambiguous and meaningful beyond just its name.
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?
It provides concrete use cases such as SEO analysis, competitor research, and search ranking monitoring, plus billing context. There are no explicit when-not-to-use instructions, but no sibling tools exist to differentiate against.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityCmaintenanceProvides real-time Google search results (organic + knowledge graph) with country targeting, language, time filters, and pagination, at low cost.110MIT
Crawlora MCPofficial
AlicenseCqualityAmaintenanceHosted MCP server for structured public web data — 319 tools across search, maps, commerce, social & finance, returning clean JSON.1003741MIT- Alicense-qualityCmaintenanceSearch Google and major search engines through Talordata SERP API for AI agents and RAG workflows.MIT