Skip to main content
Glama
Sign In
PubMed MCP Server

PubMed MCP Server

by wjixiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

PubMed Search

pubmed_search
Read-only

Search PubMed for articles by keyword. Filter by date range, publication type, and sort results by relevance or date.

Instructions

Search PubMed for articles by keyword. Returns a list of article profiles with PMID, title, authors, journal citation, and snippet. Supports date-range filters (YYYY:YYYY), publication-type filters (e.g. "clinical trial", "review"), sorting, and pagination.

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": {
      "term": "<term>"
    },
    "name": "pubmed_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed, defaults to 1)
sortNoSort order: match (relevance), date, pubdate, fauth (first author), jour (journal)match
termYesSearch query (free-text, e.g. "cancer immunotherapy")
filterNoFilters: date ranges like "2020:2024", publication types like "clinical trial", "review", "systematic review", "meta-analysis", "randomized controlled trial", "books and documents"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. Description adds that it returns a list with specific fields and supports filtering/sorting/pagination, which goes beyond annotations without contradiction.

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, front-loaded with main purpose and return value, followed by supported features. No unnecessary words.

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

Completeness5/5

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

Given it's a search tool without output schema, description sufficiently covers return format and all capabilities. Parameter details are fully provided in schema. Sibling tool exists for detail retrieval, making this complete.

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 coverage is 100% with descriptions for all 4 parameters. Description adds context like date format 'YYYY:YYYY' and examples of publication types ('clinical trial', 'review'), enhancing understanding beyond schema.

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?

Clearly states it searches PubMed for articles by keyword and lists returned fields (PMID, title, authors, journal citation, snippet). Distinguishes from sibling tool pubmed_article_detail which likely gets article details.

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?

Describes supported filters (date ranges, publication types), sorting, and pagination. Implicitly contrasts with sibling by focusing on search vs. detail retrieval, but does not explicitly state when not to use.

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

Deploy Server

Other Tools