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

google-scholar-search-mcp

by LWaetzig

get_paper_details

Retrieve full details for a specific paper by scholar ID or title, using an earlier search result's ID to avoid mismatches and ensure accurate paper metadata.

Instructions

Get full details of a specific paper.

Identify the paper with scholar_id from an earlier search result when you have one; a title search takes the first hit, which can be a different paper.

Args: title (str | None): The exact (or close) title of the paper. scholar_id (str | None): scholar_id of a paper from an earlier search result.

Returns: PaperDetails: Details of the best-matching paper.

Raises: ScholarBlockedError: If Google Scholar blocks the client. ScholarRateLimitError: If Google Scholar throttles the request after retries. ScholarInvalidArgumentError: If no identifier is given. ScholarNotFoundError: If nothing matches.

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

Input Schema

NameRequiredDescriptionDefault
titleNo
scholar_idNo

Output Schema

NameRequiredDescriptionDefault
urlNo
yearNo
titleYes
venueNo
bibtexNo
authorsNo
pub_urlNo
abstractNo
scholar_idNo
num_citationsNo
public_accessNo
cites_per_yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.4.0
    • addedInput schema / properties / scholar_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Scholar Id"
      +}
    • addedInput schema / properties / title / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / title / default
      Added value: +null
    • removedInput schema / properties / title / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "title"
      -]
    • removedOutput schema / properties / author_pub_id
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Author Pub Id"
      -}
  2. First observedv0.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses matching behavior ('best-matching paper', first-hit risk), and enumerates the failure modes including blocking, throttling after retries, missing identifier, and no match. It does not describe pagination or result size, but those are largely moot for a single-record fetch.

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 one-line purpose, then structured Args/Returns/Raises sections that are easy to scan. The scholar_id note appears twice (prose and Args), a small redundancy, but nothing is padding.

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?

For a two-optional-parameter lookup tool with an output schema already defining PaperDetails, the description covers input choice, matching behavior, and error conditions. The only residual gap is not stating explicitly that one of the two arguments must be provided.

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 description coverage is 0%, so the description must compensate, and it does via an Args block: title is 'exact (or close)' implying fuzzy matching, and scholar_id is tied to provenance from an earlier search. The requirement that at least one identifier be supplied is only conveyed indirectly through the ScholarInvalidArgumentError entry.

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?

"Get full details of a specific paper" gives a clear verb (get) and resource (paper details) with an explicit scope of 'full details'. It implicitly contrasts with search/listing siblings by framing this as single-paper retrieval, but never names get_bibtex or get_citations to distinguish which detail-retrieval tool to pick.

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 gives concrete when-to-use guidance: prefer scholar_id from an earlier search result, and warns that a title search returns the first hit, which may be a different paper. It stops short of naming sibling tools or stating exclusions beyond the title-vs-id tradeoff.

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