Skip to main content
Glama
google-scholar-search-mcp

google-scholar-search-mcp

by LWaetzig

bulk_search

Run multiple Google Scholar queries sequentially with rate limiting for batch literature reviews, returning results and per-query errors without aborting the batch.

Instructions

Search Google Scholar for multiple queries sequentially with rate limiting.

Use this for batch literature reviews. Each query runs one at a time with delays between them to avoid being blocked. Only first pages are returned; to see more of one query, call search_papers with its next_offset.

Args: queries (list[str]): List of search queries (maximum 10). max_results_per_query (int): Results per query (1-10, default 5). year_from (int | None): Filter to papers published in or after this year. year_to (int | None): Filter to papers published in or before this year.

Returns: BulkSearchResponse: One result per query plus per-query errors; failed queries do not abort the batch.

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": {
      "queries": "<queries>"
    },
    "name": "bulk_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYes
year_toNo
year_fromNo
max_results_per_queryNo

Output Schema

NameRequiredDescriptionDefault
errorsNo
resultsYes
total_queriesYes
completed_queriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.4.0
    • removedOutput schema / $defs / PaperResult / properties / author_pub_id
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Author Pub Id"
      -}
    • addedOutput schema / $defs / SearchResponse / properties / next_offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Next Offset"
      +}
    • addedOutput schema / $defs / SearchResponse / properties / offset
      Added value: +{
      +  "default": 0,
      +  "title": "Offset",
      +  "type": "integer"
      +}
  2. First observedv0.0.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does most of it: it discloses sequential execution, inter-query delays to avoid blocking, the first-page-only truncation limit, and that failed queries do not abort the batch. Remaining gaps are auth/quota requirements and any sense of expected wall-clock duration for a 10-query batch.

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

Conciseness4/5

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

Front-loaded purpose sentence, then a scoping/alternative note, then a compact Args/Returns block — well structured and easy to scan. Minor redundancy in restating schema types such as (list[str]) and the default value, but no sentence is wasted.

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?

For a 4-parameter batch tool with an output schema present, this covers what the description must: purpose, routing to the sibling, batch semantics, and partial-failure behavior. Return shape is documented by the output schema, and the description still adds the useful note that per-query errors are returned alongside results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must define every parameter, and it does: queries as a list capped at 10, max_results_per_query bounded 1-10 with default 5, and year_from/year_to expressed as inclusive publication-year filters with nullability implied. This fully compensates for the bare 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?

States a specific verb and resource ("Search Google Scholar for multiple queries sequentially") and pins the distinguishing trait versus siblings: batch, sequential execution with rate limiting, first-pages-only. An agent can tell immediately that this is the multi-query batch entry point rather than the single-query search_papers.

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

Usage Guidelines5/5

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

Gives an explicit use case ("Use this for batch literature reviews") and routes the agent to the alternative with an actionable condition: "Only first pages are returned; to see more of one query, call search_papers with its next_offset." The division of labor between the batch and single-query tools is unambiguous.

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