Google Scholar MCP Server

get_article_versions

Retrieve all versions of a scholarly article from multiple sources using its cluster ID from search results.

Instructions

Get all versions of a specific article from different sources.

Use the cluster_id from search_articles results.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_article_versions"
  }
}

Input Schema

Name	Required	Description	Default
`cluster_id`	Yes	Cluster ID from a previous search result

Output Schema

Name	Required	Description	Default
`versions`	Yes
`cluster_id`	Yes
`total_versions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jul 6, 2026

TDQS

A4.1/5.0

Behavior2/5

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

No annotations are provided, so the description should disclose behavioral traits. It does not mention if the operation is read-only, return format, pagination, or any limits. This is a significant gap.

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?

Two concise sentences, both necessary: first states purpose, second gives usage guidance. No wasted words.

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 tool with one parameter and full schema coverage, the description is complete. It tells what to do and where to get the input. An output schema exists to handle return values, so description doesn't need to cover that.

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?

The schema already describes cluster_id as 'Cluster ID from a previous search result'. The description adds value by specifying that it comes from search_articles, providing helpful context beyond the 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?

The description clearly states the action 'Get all versions of a specific article from different sources', which is specific and distinguishes it from siblings like search_articles (searching) and get_fulltext (full text).

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 instruction 'Use the cluster_id from search_articles results' provides clear context for when to use this tool, but it does not explicitly mention alternatives or when not to use it.

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

Deploy Server