Skip to main content
Glama
garylab

Serper MCP Server

by garylab

google_search_news

Search Google News for current articles by entering a query and filtering by country, language, location, and time period. Retrieve relevant news results for timely information.

Instructions

Search Google for results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesThe query to search for
glNoThe country to search in, e.g. us, uk, ca, au, etc.
locationNoThe location to search in, e.g. San Francisco, CA, USA
hlNoThe language to search in, e.g. en, es, fr, de, etc.
pageNoThe page number to return, first page is 1 (integer value as string)1
tbsNoThe time period to search in, e.g. d, w, m, y
numNoThe number of results to return, max is 100 (integer value as string)10

Implementation Reference

  • SearchRequest schema is used as the input schema for google_search_news (same as google_search, google_search_images, google_search_videos).
    class SearchRequest(BaseRequest):
        tbs: Optional[str] = Field(
            None, description="The time period to search in, e.g. d, w, m, y"
        )
        num: str = Field(
            "10",
            pattern=r"^([1-9]|[1-9]\d|100)$",
            description="The number of results to return, max is 100 (integer value as string)",
        )
  • Registration of google_search_news in the google_request_map, mapping it to SearchRequest schema.
    SerperTools.GOOGLE_SEARCH_NEWS: SearchRequest,
  • Enum definition for the google_search_news tool name/value.
    GOOGLE_SEARCH_NEWS = "google_search_news"
  • The call_tool handler dispatches google_search_news to the generic google() function via the google_request_map lookup.
    if name == SerperTools.WEBPAGE_SCRAPE.value:
        request = WebpageRequest(**arguments)
        result = await scape(request)
        return [TextContent(text=json.dumps(result, indent=2), type="text")]
    
    if not SerperTools.has_value(name):
        raise ValueError(f"Tool {name} not found")
    
    tool = SerperTools(name)
    request = google_request_map[tool](**arguments)
    result = await google(tool, request)
    return [TextContent(text=json.dumps(result, indent=2), type="text")]
  • The google() handler - for google_search_news, it extracts 'news' from the tool value and calls https://google.serper.dev/news.
    async def google(tool: SerperTools, request: BaseModel) -> Dict[str, Any]:
        uri_path = tool.value.split("_")[-1]
        url = f"https://google.serper.dev/{uri_path}"
        return await fetch_json(url, request)
Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It gives no information about return type, pagination, or that it specifically returns news articles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but lacks substance. It is under-specified, not concise in a helpful way.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is completely inadequate for a tool with 7 parameters. It does not mention that it searches news, how to use time filtering (tbs), or what results to expect.

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 parameters are well-documented in the schema. The description adds no additional meaning, but the baseline is 3 per the guidelines.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search Google for results' is a tautology of the tool name and does not specify that it searches for news. It fails to distinguish from siblings like google_search (general web) or google_search_images.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives. The description does not mention that it is for news or provide any context for selection among the many sibling search tools.

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/garylab/serper-mcp-server'

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