Skip to main content
Glama
Serper Search MCP Server

Serper Search MCP Server

by NightTrek

serper-google-search

Performs Google searches via the Serper API and returns knowledge graph, organic results, related questions, and other rich data for research and app integration.

Instructions

Perform a Google search using the SERPER API. Returns rich search results including knowledge graph, organic results, related questions, and more.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "serper-google-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
glNoCountry code (e.g., "us", "uk")
hlNoLanguage code (e.g., "en", "es")
queryYesSearch query
numResultsNoNumber of results to return (default: 10)
autocorrectNoEnable query autocorrection

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses some return content (knowledge graph, organic results, related questions), but omits rate limits, authentication needs, pagination or truncation behavior, and result ordering details.

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 tightly written sentences with zero waste, and the core action is front-loaded. The brief return-content summary earns its place by indicating output breadth.

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?

No output schema exists, so the description should explain returns more fully; it lists categories but ends with vague "and more." For a search tool with five parameters, it is adequate but leaves gaps around authentication, rate limits, and exact result formatting.

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 input schema already documents all five parameters. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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 states a specific verb and resource: "Perform a Google search using the SERPER API." It clearly indicates the tool's function, though it has no sibling alternatives to differentiate against.

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

Usage Guidelines2/5

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

It provides no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The usage context is only implied by the generic search purpose.

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

Deploy Server

Other Tools