Skip to main content
Glama

Pubmed Search Articles

pubmed_search_articles
Read-only

Search PubMed using full query syntax with filters for date range, author, journal, MeSH terms, language, species, and free full text. Returns PMIDs with optional summaries, supporting pagination.

Instructions

Search PubMed with full query syntax, filters, and date ranges. Returns PMIDs and optional brief summaries. Supports field-specific filters (author, journal, MeSH terms), common filters (language, species, free full text), and pagination via offset for paging through large result sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesPubMed search query (supports full NCBI syntax)
maxResultsNoMaximum results to return
offsetNoResult offset for pagination (0-based)
sortNoSort order: relevance (default), pub_date (newest first), author, or journalrelevance
dateRangeNoFilter by date range. The filter is applied only when both `minDate` and `maxDate` are non-empty; either one empty disables the entire date range.
publicationTypesNoFilter by publication type (e.g. "Review", "Clinical Trial", "Meta-Analysis"). Multiple values are OR'd — any match qualifies.
authorNoFilter by author name (e.g. "Smith J")
journalNoFilter by journal name
meshTermsNoFilter by MeSH terms. Multiple terms are AND'd — all must match.
languageNoFilter by language (e.g. "english")
hasAbstractNoOnly include articles with abstracts
freeFullTextNoOnly include free full text articles
speciesNoFilter by species
summaryCountNoFetch brief summaries for top N results (0 = PMIDs only)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesOriginal query
offsetYesResult offset used
pmidsYesPubMed IDs
summariesYesBrief summaries (empty array when summaryCount is 0)
searchUrlYesPubMed search URL
effectiveQueryYesSanitized query sent to PubMed after applying all active filters
totalFoundYesTotal matching articles
appliedFiltersYesNormalized filter values that were applied to the PubMed query
noticeNoOptional guidance when results are empty or paging overshot — e.g. how to broaden filters or reset offset. Absent on successful result pages.
Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds context about return values (PMIDs, optional summaries) and supported filters, which is helpful beyond annotations. No contradictions.

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?

Two concise sentences: first states purpose and output, second lists key features. No wasted words, and the most critical information is front-loaded.

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?

With 14 parameters and full schema coverage, the description covers the main purpose and key capabilities. It does not mention error handling or rate limits, but the annotations and output schema provide sufficient completeness for a search tool.

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 coverage is 100%, so baseline is 3. The description groups filters (author, journal, MeSH terms, etc.) but does not add new meaning beyond the schema's individual parameter descriptions.

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 PubMed with full query syntax, filters, and date ranges, and returns PMIDs with optional summaries. It differentiates from sibling tools like pubmed_fetch_articles and pubmed_convert_ids by specifying its search role.

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

Usage Guidelines3/5

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

The description implies usage for searching PubMed but does not explicitly state when to use versus sibling tools like pubmed_europepmc_search or pubmed_fetch_articles. No exclusions or alternative guidance is provided.

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