PubMed MCP Server

search_by_journal

Locate articles in a specific journal by providing journal name, keywords, and optional date range to get PubMed citations.

Instructions

Search articles within specific journal(s)

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": {
      "journal_name": "<journal_name>"
    },
    "name": "search_by_journal"
  }
}

Input Schema

Name	Required	Description
`journal_name`	Yes	Journal name or abbreviation
`keywords`	No	Additional keywords to search within the journal
`date_from`	No	Start date (YYYY/MM/DD)
`date_to`	No	End date (YYYY/MM/DD)
`max_results`	No	Maximum results (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description bears full burden for behavioral disclosure, but it only describes the basic function without detailing behavior like search scope, error handling, or result format, leaving significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, highly concise with no wasted words; while efficient, it could be more structured or front-loaded with critical information.

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

Completeness2/5

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

Given the absence of output schema, the description should explain return values or behavior, but it does not. The tool has moderate complexity (5 parameters), yet the description leaves the agent uninformed about results or side effects.

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 five parameters are fully described in the input schema (100% coverage), so the description adds no extra meaning beyond the schema; baseline score of 3 is appropriate.

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 'Search articles within specific journal(s)' clearly identifies the core action (search) and resource (articles), and specifies the filter (specific journals), effectively distinguishing it from sibling tools like 'search_articles' and 'search_by_author'.

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 when a journal name is known, but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or context about its suitability compared to sibling search tools.

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

Deploy Server