Skip to main content
Glama

Pubmed Europepmc Search

pubmed_europepmc_search
Read-only

Search Europe PMC for biomedical literature including preprints, patents, and Agricola records beyond PubMed. Use fielded queries and pagination to retrieve abstracts, citations, and open access full text.

Instructions

Search Europe PMC, a broad open-access biomedical corpus. Surfaces preprints (source: PPR), patents (source: PAT), Agricola (source: AGR), plus everything in PubMed (MED) and PMC. Use when additional coverage is needed — preprints and EPMC-only OA records are the typical recovery. Paginate via cursorMark. Defaults to MED, PMC, and PPR; pass sources to include PAT / AGR.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesEurope PMC search query. Supports field tokens like `AUTH:"<name>"`, `JOURNAL:"<title>"`, `TITLE:"<words>"`, `PUB_YEAR:[2020 TO 2024]`, `DOI:"..."`, `EXT_ID:"<pmid>" AND SRC:MED`. Free text is matched broadly across abstract/title/keywords.
pageSizeNoResults per page. Max 100 per EPMC API.
cursorMarkNoPagination cursor. Use `*` (default) for the first page; pass the previous response's `nextCursorMark` for subsequent pages.*
sourcesNoFilter to specific EPMC sources. Defaults to MED, PMC, PPR when omitted. Pass an explicit array including PAT or AGR to broaden coverage. Allowed values: MED, PMC, PPR, PAT, AGR.
resultTypeNo`core` returns abstract, IDs, dates, license; `lite` is a smaller payload with IDs and titles only.core
sortNoOptional EPMC sort: `<field> asc|desc`. Documented sortable fields: `P_PDATE_D` (publication date), `CITED` (citation count), `AUTH_FIRST` (first author surname), `PUB_YEAR` (publication year). Examples: `P_PDATE_D desc` (newest first), `CITED desc` (most cited). Omit for relevance ranking. Fields outside the documented set are rejected by EPMC.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsYesMatching Europe PMC records, in the order EPMC returned them
cursorMarkYesCursor used for this response (echoed from the request)
nextCursorMarkNoCursor to pass back as `cursorMark` for the next page. Absent on the final page.
searchUrlYesEurope PMC's website search URL for this query
queryYesEffective query string echoed by Europe PMC
hitCountYesTotal matching records across all pages
appliedSourcesYesSources the query was filtered against (defaults applied)
noticeNoOptional guidance when results are empty or paging overshot
Behavior3/5

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

Annotations already declare readOnlyHint: true and openWorldHint: true. The description adds defaults for sources and pagination mechanism but does not disclose additional behavioral traits like rate limits or response volume. It is adequate but adds limited value beyond annotations.

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 two sentences plus a note on pagination and defaults. It is front-loaded with the main purpose and each sentence is informative without waste.

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 complexity (6 parameters, 1 required) and presence of output schema, the description covers key usage aspects: source selection, pagination, default behavior. Could mention that results are article objects, but output schema likely handles 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?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining default sources, the purpose of including different sources, and pagination with cursorMark, going beyond what schema descriptions provide.

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 it searches Europe PMC, a biomedical corpus, and lists specific sources (preprints, patents, Agricola, PubMed, PMC). It distinguishes from sibling tools by highlighting additional coverage (preprints and EPMC-only OA records).

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 explicitly states when to use this tool ('when additional coverage is needed') and mentions pagination via cursorMark. It does not explicitly exclude use cases, but the context of sibling tools implies alternatives.

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/cyanheads/pubmed-mcp-server'

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