Skip to main content
Glama

Serper

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search

search
Read-onlyIdempotent

Google web search via Serper: returns organic results (title, link, snippet, position), an answer box if present, and a knowledge graph summary. Accepts query, result count (max 20), and optional country code (gl) and location for geo-targeted results.

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. "best espresso machine 2026"
_apiKeyNoOptional — your own Serper API key for higher limits; omit to use the shared Pipeworx key.
locationNoLocation string, e.g. "San Francisco, California, United States"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-serper-api-key",
+    "num": 10,
+    "query": "best espresso machine 2026"
+  },
+  {
+    "_apiKey": "your-serper-api-key",
+    "gl": "us",
+    "location": "San Francisco, California, United States",
+    "num": 15,
+    "query": "python machine learning libraries"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The description adds value beyond annotations by detailing the types of results returned (organic results with title, link, snippet, position; answer box; knowledge graph). It also notes constraints like max 20 results. No contradiction with annotations.

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?

The description is two sentences long, front-loads the main purpose, and contains no superfluous information. Every word is earned.

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?

Despite no output schema, the description fully explains the return value components (organic results with details, answer box, knowledge graph). This makes it complete for a search tool.

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 coverage is 100%, so baseline is 3. The description adds meaning by stating 'result count (max 20)' and 'optional country code (gl) and location for geo-targeted results', which supplements the schema descriptions.

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 it is a Google web search via Serper, specifying the resources returned (organic results, answer box, knowledge graph) and parameters. This distinguishes it from siblings like 'news', 'deep_research', and 'places'.

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?

The description explains how to use the tool with query, result count, country, and location parameters. However, it does not explicitly contrast with alternatives (e.g., when to use 'deep_research' instead), leaving some ambiguity.

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