Skip to main content
Glama
serper-search-mcp-server

serper-search-mcp-server

search_scholar

Search Google Scholar for academic publications with authors, journals, years, and citation counts, supporting recency filters and language options for literature reviews.

Instructions

Google Scholar search via Serper API. Returns academic publications with authors, journal, year, and citation counts. Ideal for research papers and literature reviews.

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": "search_scholar"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesAcademic search query (max 400 chars / 50 words).
countryNoISO 3166-1 alpha-2 country code (e.g. "US", "GB"). Default: "US".
ui_langNoUI language (e.g. "en-US"). Default: "en".
freshnessNoTime filter: pd=past day pw=week pm=month py=year any=none (historical). Pass pd/pw/pm/py whenever the user asks for latest/current/recent results ("today", "this week", "latest", current year); omit or "any" for timeless or historical questions. The response footer echoes the filter that was applied.
num_resultsNoResults (1–20, default 10). Note: >10 results uses 2 Serper credits.
search_langNoLanguage code (e.g. "en", "de"). Default: "en".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.1.0
    • changedInput schema / properties / freshness / description
      Previous value: -"Time filter: pd=day pw=week pm=month py=year."New value: +"Time filter: pd=past day pw=week pm=month py=year any=none (historical). Pass pd/pw/pm/py whenever the user asks for latest/current/recent results (\"today\", \"this week\", \"latest\", current year); omit or \"any\" for timeless or historical questions. The response footer echoes the filter that was applied."
    • changedInput schema / properties / freshness / enum
      Previous value: -[
      -  "pd",
      -  "pw",
      -  "pm",
      -  "py"
      -]New value: +[
      +  "pd",
      +  "pw",
      +  "pm",
      +  "py",
      +  "any"
      +]
  2. First observedv4.0.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden and does partially discharge it by enumerating the returned fields. It says nothing about credit cost, rate limits, authentication, or result capping, though the input schema mentions credit behavior for num_results.

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?

Three short sentences, each carrying distinct information: source, return shape, and intended use. Nothing is redundant and the identification of the tool comes first.

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?

With no output schema, the description usefully compensates by naming the returned fields (authors, journal, year, citation counts). What remains thin is operational context such as result limits and credit usage, though much of that is covered by the schema text.

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%, including the freshness enum semantics and credit notes, so the schema already documents all six parameters thoroughly. The description adds no parameter-level guidance beyond the schema, which is the baseline 3 case.

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 pairs a specific verb and resource ("Google Scholar search") with the returned entity type ("academic publications with authors, journal, year, and citation counts"), which clearly separates it from general web or news search siblings. It stops short of naming or contrasting any sibling tool, so the agent must infer the boundary itself.

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?

"Ideal for research papers and literature reviews" gives a clear usage context that an agent can match against a query. There are no explicit exclusions or named alternatives (e.g., when to fall back to search_web or deep_research), which keeps it below a 5.

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