Skip to main content
Glama
AceDataCloud

SerpMCP

by AceDataCloud
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

serp_google_search

Search Google and retrieve structured JSON results including web pages, images, news, maps, local places, and videos. Supports localized searches, time filters, and pagination for comprehensive data retrieval.

Instructions

Search Google and get structured results using the SERP API.

Performs a Google search and returns the complete JSON response from the API,
preserving all available fields and data.

Args:
    query: The search query string. Required.
    search_type: Type of search to perform. Options:
        - "search": Regular web search (default)
        - "images": Image search
        - "news": News articles
        - "maps": Map results
        - "places": Local business/place results
        - "videos": Video results
    country: Country code for localized results (e.g., "us", "cn", "uk").
        Default is "us".
    language: Language code for results (e.g., "en", "zh-cn", "fr").
        Default is "en".
    time_range: Time filter for results. Options:
        - "qdr:h": Past hour
        - "qdr:d": Past day
        - "qdr:w": Past week
        - "qdr:m": Past month
        - None: No time restriction (default)
    number: Number of results per page (default: 10).
        Note: More than 10 results may incur additional credits.
    page: Page number for pagination (default: 1).

Returns:
    Complete JSON response from the SERP API containing all available data.

Example:
    serp_google_search(query="artificial intelligence", search_type="news")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query string. Required.
search_typeNoType of search to perform. Options: 'search' (regular web search, default), 'images' (image search), 'news' (news articles), 'maps' (map results), 'places' (local business/place results), 'videos' (video results).search
countryNoCountry code for localized results (e.g., 'us', 'cn', 'uk'). Default is 'us'.
languageNoLanguage code for results (e.g., 'en', 'zh-cn', 'fr'). Default is 'en'.
time_rangeNoTime filter for results. Options: 'qdr:h' (past hour), 'qdr:d' (past day), 'qdr:w' (past week), 'qdr:m' (past month), or None for no time restriction (default).
numberNoNumber of results per page (default: 10). Note: More than 10 results may incur additional credits.
pageNoPage number for pagination (default: 1).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses return format (complete JSON), default values, and a credit note for result count. However, it does not discuss auth requirements, rate limits, or potential side effects.

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?

Structured with Args, Returns, Example sections. Clear bullet points for enums. Concise enough while covering all 7 parameters. Slightly verbose but well-organized.

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?

Given the 7 parameters, all with descriptions, and an output schema presumed, the description covers search functionality thoroughly. Includes pagination, localization, time filters, and a credit warning. Suitable for a general search tool.

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 baseline is 3. The description adds some value with an example and a credit-related note for the number parameter, but largely restates schema information.

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?

The description clearly states the tool searches Google via SERP API and returns structured results. It enumerates search types, but doesn't explicitly distinguish from sibling tools that specialize in each type.

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 details parameters and defaults, but does not provide explicit guidance on when to use this general tool versus the specialized siblings (e.g., serp_google_images). Usage context is implied through search_type parameter.

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/AceDataCloud/SerpMCP'

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