Skip to main content
Glama

paper_download

Download academic paper PDFs from multiple sources including arXiv, PubMed, bioRxiv, and Semantic Scholar using platform-specific identifiers.

Instructions

Download academic paper PDFs from multiple sources.

Input Constraints:

  • searcher: Required, must be one of the supported platforms

  • paper_id: Required, 1-200 characters, cannot be empty

Paper ID formats:

  • arXiv: Use the arXiv ID (e.g., "2106.12345").

  • PubMed: Use the PubMed ID (PMID) (e.g., "32790614").

  • bioRxiv: Use the bioRxiv DOI (e.g., "10.1101/2020.01.01.123456").

  • medRxiv: Use the medRxiv DOI (e.g., "10.1101/2020.01.01.123456").

  • Google Scholar: Direct PDF download is not supported; please use the paper URL to access the publisher's website.

  • IACR: Use the IACR paper ID (e.g., "2009/101").

  • Semantic Scholar: Use the Semantic Scholar paper ID, Paper identifier in one of the following formats:

    • Semantic Scholar ID (e.g., "649def34f8be52c8b66281af98ae884c09aef38b")

    • DOI: (e.g., "DOI:10.18653/v1/N18-3011")

    • ARXIV: (e.g., "ARXIV:2106.15928")

    • MAG: (e.g., "MAG:112218234")

    • ACL: (e.g., "ACL:W12-3903")

    • PMID: (e.g., "PMID:19872477")

    • PMCID: (e.g., "PMCID:2323736")

    • URL: (e.g., "URL:https://arxiv.org/abs/2106.15928v1")

Returns:

List of paths to the downloaded PDF files.

Example:

paper_download([ {"searcher": "arxiv", "paper_id": "2106.12345"}, {"searcher": "pubmed", "paper_id": "32790614"}, {"searcher": "biorxiv", "paper_id": "10.1101/2020.01.01.123456"}, {"searcher": "semantic", "paper_id": "DOI:10.18653/v1/N18-3011"} ])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
query_listYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes what the tool does (downloads PDFs), mentions platform-specific constraints (Google Scholar limitation), and specifies the return format ('List of paths to the downloaded PDF files'). It doesn't cover potential errors, rate limits, or authentication needs, but provides substantial operational context.

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 description is well-structured with clear sections (Input Constraints, Paper ID formats, Returns, Example) and front-loaded with the core purpose. While comprehensive, some details like the extensive Semantic Scholar formats could be slightly condensed, but overall it's efficient and informative.

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?

Given the complexity of multiple academic sources with different ID formats, no annotations, and an output schema (which handles return values), the description is complete. It covers purpose, usage constraints, parameter details with examples, return information, and includes a practical example, leaving no significant gaps for the agent.

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?

The schema description coverage is 0%, so the description must fully compensate. It provides extensive parameter semantics: it explains the 'searcher' parameter with supported platforms and format requirements for 'paper_id' across multiple sources, including detailed examples. This adds crucial meaning beyond what the bare schema provides.

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 tool's purpose: 'Download academic paper PDFs from multiple sources.' This is a specific verb ('download') + resource ('academic paper PDFs') + scope ('from multiple sources'), and it distinguishes from sibling tools like 'paper_read' and 'paper_search' which likely have different functions.

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 provides clear context for when to use this tool (to download PDFs from academic sources), and it explicitly mentions that Google Scholar doesn't support direct PDF downloads, suggesting an alternative approach. However, it doesn't explicitly compare usage with sibling tools like 'paper_search' or specify 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LinXueyuanStdio/academic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server