Scrapingdog MCP Server

Google Scholar API

google_scholar

Search academic papers, authors, and citation counts. Refine results using filters for year, language, and source type.

Instructions

Search academic papers, authors and citation counts via Google Scholar.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "google_scholar"
  }
}

Input Schema

Name	Required	Description
`page`	No	Zero-based page number. (API default: 0)
`cites`	No	Article id for 'Cited by' searches.
`query`	No	Search query (optional when using cites).
`as_sdt`	No	Search type / filter (patents, case law, courts).
`as_yhi`	No	Filter: results up to this year.
`as_ylo`	No	Filter: results from this year onward.
`results`	No	Results per page.
`language`	No	Result language code (e.g. en, es, fr, de). (API default: en)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 1, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral transparency. It only states the basic search functionality and does not disclose behaviors such as pagination, return format, rate limits, or the purpose of specific parameters like 'cites' for citation tracking.

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 a single, clear, front-loaded sentence with absolutely no filler. It efficiently communicates the core purpose without unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description is too minimal to fully inform an agent about response structure, pagination, or how to combine optional parameters. It only covers the basic action, leaving significant gaps for a tool with 8 parameters.

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?

The schema provides a 100% coverage of all 8 parameters with descriptions, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already documents, which is acceptable but not enhancing.

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 identifies the tool's function: 'Search academic papers, authors and citation counts via Google Scholar.' It uses a specific verb ('Search'), names the resource (academic papers, authors, citation counts), and distinguishes it from sibling tools like google_search or google_patents.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or sibling comparisons. The academic context is implied but not explicitly stated as a differentiator from other search tools.

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