Skip to main content
Glama

Serper

by io.github.pipeworx-io
OverviewDiscussionsAdmin

News

news
Read-onlyIdempotent

Google News search via Serper: returns recent news articles (title, link, snippet, source, date) matching the query. Accepts query, result count (max 20), and optional country code (gl).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
glNoCountry code for geolocation, e.g. "us", "gb", "de"
numNoNumber of results (default 10, max 20)
queryYesSearch query, e.g. "federal reserve rate decision"
_apiKeyNoOptional — your own Serper API key for higher limits; omit to use the shared Pipeworx key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-serper-api-key",
+    "query": "federal reserve rate decision"
+  },
+  {
+    "_apiKey": "your-serper-api-key",
+    "gl": "gb",
+    "num": 20,
+    "query": "artificial intelligence regulation"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive. Description adds context: API source (Serper), result limit (max 20), and output fields. No contradictions.

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?

Two sentences: first explains purpose and output, second lists parameters. No redundancy, efficient use of words, front-loaded.

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?

Covers purpose, parameters, output fields, and source. Missing explicit default values (e.g., default num=10), but otherwise sufficient for the agent to use correctly.

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 covers all parameters. Description adds marginal value by noting max result count and optional country code, but does not provide default values or additional constraints beyond schema.

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?

Clearly states the tool performs Google News search via Serper, returns specific fields (title, link, snippet, source, date). Distinguishes from sibling tools like 'search' and 'places' by focusing on news articles.

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?

Implicitly indicates when to use (need recent news). Mentions parameters but does not explicitly state when not to use or compare to alternatives. Sibling list provides context.

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

All Serper toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources