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

google-scholar-search-mcp

by LWaetzig

get_bibtex

Retrieve a BibTeX citation entry for a paper by title or Google Scholar ID from search results, enabling accurate citations in LaTeX and reference managers.

Instructions

Get BibTeX citation entry for a paper.

Identify the paper with scholar_id from an earlier search result when you have one.

Args: title (str | None): Title of the paper to get BibTeX for. scholar_id (str | None): scholar_id of a paper from an earlier search result.

Returns: str: BibTeX entry.

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

Input Schema

NameRequiredDescriptionDefault
titleNo
scholar_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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"
      -]
  2. First observedv0.0.0

TDQS

A3.8/5.0
Behavior4/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 it does disclose meaningful failure modes: blocking, throttling after retries, invalid-argument when no identifier is given, and not-found when nothing matches. That is genuinely useful operational context beyond the schema; it omits any statement about retry behavior, authentication, or response size.

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?

The lead sentence is front-loaded and the Args/Returns/Raises structure is scannable. The Returns line restates what the output schema already encodes, which is mild redundancy, but nothing is padded or buried.

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 read tool with an output schema present, the description covers purpose, identifier selection, and the four error cases that matter. The remaining gaps (both-params behavior, title matching semantics) are minor rather than disqualifying.

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: both parameters are named with meaning, and it establishes precedence ('use scholar_id ... when you have one'), implying the id path is preferred over title. It does not say what happens if both are supplied or how fuzzy title matching is.

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 opens with a specific verb-and-resource statement ('Get BibTeX citation entry for a paper'), so an agent immediately knows the output is a BibTeX string for one paper. It does not explicitly contrast itself with siblings like get_paper_details or get_citations, leaving the boundary to be inferred.

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

Usage Guidelines3/5

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

It gives conditional guidance for invocation ('identify the paper with scholar_id from an earlier search result when you have one'), implying this tool is called after a search. There is no statement of when to prefer a sibling such as get_paper_details instead, or what to do if neither identifier is available.

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