OpenAlex MCP Server

openalex_batch_get_works

Retrieve information for multiple academic papers in a single request, improving efficiency over individual lookups. Supports up to 50 OpenAlex IDs and optional abstract inclusion.

Instructions

Get information for multiple papers in one request. More efficient than calling get_work multiple times.

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": {
      "work_ids": "<work_ids>"
    },
    "name": "openalex_batch_get_works"
  }
}

Input Schema

Name	Required	Description	Default
`work_ids`	Yes	Array of paper IDs (OpenAlex IDs only, max 50)
`include_abstract`	No	Include abstracts in response (default: false for performance)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Jun 22, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions the max 50 IDs in the schema but does not disclose behavioral traits like id validation, error handling, or performance impact. This is adequate but lacks depth.

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?

The description is extremely concise with two sentences, no wasted words. It front-loads the main purpose and efficiently indicates efficiency benefit.

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?

Given the simplicity of the tool (batch get) and absence of output schema, the description is mostly complete. It covers purpose and efficiency. However, it does not mention return format or error behavior, which would be helpful for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, as both parameters are described in the input schema. The description does not add new information beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 information) and the resource (multiple papers) with a specific verb and resource. It also distinguishes from the sibling tool 'get_work' by implying batch vs single, fulfilling the criterion for specific verb+resource and sibling differentiation.

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 identifies when to use this tool ('for multiple papers') and contrasts with an alternative ('more efficient than calling get_work multiple times'). It does not explicitly state when not to use it or context exclusions, but it provides clear usage context.

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

Deploy Server