Skip to main content
Glama
oksure

OpenAlex Research MCP Server

by oksure

search_in_journal_list

Filter academic papers to those published in prestigious journal or conference lists (UTD24, FT50, AJG 4*, etc.) for high-quality, credibility-gated searches. Combine with institutional filters for targeted results.

Instructions

Search for papers in a named list of top journals or conferences (preset) rather than specifying individual venues. This is the main tool for credibility-gated searches. Examples: search in UTD24 journals, FT50, AJG 4*, top AI conferences. Combine with author_institution or institution_group to answer questions like "AI papers in top AI conferences by Harvard/Stanford/MIT authors".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoTopic or keyword query (e.g., "artificial intelligence", "LLMs", "supply chain"). For exact phrase matching (e.g., 'privacy paradox' as a specific concept), set exact_phrase to true.
exact_phraseNoSet to true for exact phrase matching. Without this, search terms are matched independently. Use this when searching for a specific concept or multi-word term (e.g., 'privacy paradox', 'supply chain resilience').
search_fieldNoRestrict search to a specific field: 'title' (paper titles only), 'abstract' (abstracts only), or 'fulltext' (full text only). By default, searches across all fields. Cannot be combined with exact_phrase.
journal_listYesPreset journal list key. Use list_journal_presets to see all options. Common values: utd24, ft50, abs4star, abs4, abs3, top_ai_conferences, ms_misq_ops, nature_science, top_cs_conferences
from_yearNoFrom publication year
to_yearNoTo publication year
min_citationsNoMinimum citation count (default: 0 = no filter)
author_institutionNoOnly papers by authors at this institution. Single name or pipe-separated OR list. E.g., "INSEAD" or "Harvard University|Stanford University"
institution_groupNoNamed institution group: harvard_stanford_mit, ivy_league, top_us, top_us_business, insead_london, top_global_business, top_china
sortNoSort: cited_by_count:desc (default), publication_year:desc, relevance_score
per_pageNoResults per page (default: 10, use 20 for broader coverage, max: 200)
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It implies a read-only search but does not mention data source, result limits beyond schema, or any side effects. The focus is on usage context rather than behavioral details.

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?

Three sentences, each earning its place: purpose, role, and examples. Front-loaded with the core idea, no redundant or filler content.

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 11 parameters and no output schema, the description effectively orients the user with a clear use case and examples. It could mention the data source or result format for full completeness, but it covers the essential context for correct invocation.

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%, so baseline is 3. The description adds value by illustrating combinations (e.g., with author_institution) but does not explain parameters beyond what the schema already 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 searches papers in preset journal/conference lists, distinguishing it from tools that search individual venues or general topics. Examples like 'UTD24 journals, FT50, AJG 4*' reinforce the specific resource.

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?

It explicitly calls this 'the main tool for credibility-gated searches' and demonstrates combining with other parameters via examples. However, it does not list alternatives or when not to use it, leaving some ambiguity among the many sibling tools.

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/oksure/openalex-research-mcp'

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