OpenAlex MCP Server

openalex_search

Search academic papers by keywords, returning metadata including title, authors, venue, year, citation count, and open access status.

Instructions

Search for academic papers in OpenAlex database by keywords. Returns simplified paper metadata with title, authors, publication venue, year, citation count, and open access status.

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": {
      "query": "<query>"
    },
    "name": "openalex_search"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Search keywords to find papers by title
`max_results`	No	Number of results per page (default: 20, max: 200)
`page`	No	Page number for pagination (default: 1)
`sort_by`	No	Sort field and order, e.g., "cited_by_count:desc", "publication_year:desc"
`filters`	No	Filters to apply to search

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.6Jun 22, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description should disclose key behaviors. It only states the return type (simplified metadata) but omits pagination behavior, sorting, filtering, or rate limits. The schema covers sorting and filtering but the description itself is insufficient.

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 concise (two sentences) and front-loaded with purpose. Every word adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high schema coverage and no output schema, the description is adequate but incomplete. It lacks behavioral details like pagination limits and sorting options, which are covered in the schema but not referenced in the description.

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?

All parameters are described in the schema (100% coverage), so the baseline is 3. The description adds little beyond the schema; it mentions 'keywords' but does not elaborate on other parameters like max_results or filters.

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 searches for academic papers by keywords in OpenAlex and lists the returned metadata fields. This distinguishes it from sibling tools like 'openalex_get_work' which retrieves a single work by ID.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., openalex_get_work for known IDs). The description does not mention appropriate contexts or exclusions.

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

Deploy Server