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

google-scholar-search-mcp

by LWaetzig

get_citations

Retrieve papers that cite a given paper by title or Scholar ID, with pagination and max results to track citation impact.

Instructions

Get papers that cite a given paper.

With only scholar_id the cited paper's title is not fetched (one request fewer) and is omitted. To page, call again with offset set to the next_offset of the previous response (None: no more), and prefer scholar_id for the following pages.

Args: title (str | None): Title of the paper whose citations to retrieve. max_results (int): Maximum citing papers to return (1-20, default 10). scholar_id (str | None): scholar_id of a paper from an earlier search result. offset (int): Number of citing papers to skip (default 0). Scholar serves at most the first 1000.

Returns: CitationResponse: Citing papers, the cited paper's title and the total citation count when known, and offset / next_offset for paging.

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_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
offsetNo
scholar_idNo
max_resultsNo

Output Schema

NameRequiredDescriptionDefault
offsetNo
citationsYes
next_offsetNo
total_citationsNo
cited_paper_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv2.4.0
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "title": "Offset",
      +  "type": "integer"
      +}
    • 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 / $defs / PaperResult / properties / author_pub_id
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Author Pub Id"
      -}
    • addedOutput schema / properties / cited_paper_title / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / cited_paper_title / default
      Added value: +null
    • removedOutput schema / properties / cited_paper_title / type
      Removed value: -"string"
    • addedOutput schema / properties / next_offset
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Next Offset"
      +}
    • addedOutput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "title": "Offset",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / total_citations / anyOf
      Added value: +[
      +  {
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / total_citations / default
      Added value: +null
    • removedOutput schema / properties / total_citations / type
      Removed value: -"integer"
    • changedOutput schema / required
      Previous value: -[
      -  "cited_paper_title",
      -  "total_citations",
      -  "citations"
      -]New value: +[
      +  "citations"
      +]
  2. First observedv0.0.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose real behavioral traits: a cost/benefit tradeoff for scholar_id-only calls, the 1000-result ceiling enforced by Scholar, the offset/next_offset paging contract, and four distinct failure modes including blocking, throttling after retries, invalid arguments, and no-match. It does not explain retry counts, timeouts, or whether the 20-item cap is a hard client limit, but the safety-relevant behavior is largely covered.

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?

Purpose is front-loaded in a single sentence, then organized into Args/Returns/Raises so an agent can scan to the section it needs. The content earns its place, though the Returns block largely restates what the output schema already defines, and the parenthetical about 'one request fewer' is slightly awkward phrasing.

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 lookup tool with an output schema present, nothing an agent needs is missing: identifiers, limits, paging, and error conditions are all documented. The description need not describe return values further given the output schema, yet the brief Returns note usefully flags that the cited title may be absent.

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 Args block is doing all the work, and it succeeds: title vs scholar_id semantics, the 1-20 range and default of 10 for max_results, and the meaning of offset plus its 1000-record bound. The subtle interaction between scholar_id and title fetching is also explained, which the bare schema cannot convey.

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 opening sentence gives a specific verb and resource: 'Get papers that cite a given paper.' The direction of the citation relation is unambiguous, which is the main failure mode for this kind of tool. It never names the sibling tools (get_paper_details, search_papers) that an agent might confuse it with, so differentiation is implicit rather than stated.

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?

'With only scholar_id the cited paper's title is not fetched (one request fewer)' and 'prefer scholar_id for the following pages' give concrete selection rules between the two identifier parameters. The paging procedure (re-call with offset set to the previous next_offset, None means exhausted) is spelled out explicitly. There is no statement of when NOT to use this tool or which sibling to pick for a different citation need.

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