Skip to main content
Glama

build_research_timeline

Construct a research timeline for any biomedical topic or specific PMIDs, automatically detecting key milestones such as clinical trials, approvals, and landmark studies.

Instructions

Build a research timeline for a topic OR specific PMIDs.

═══════════════════════════════════════════════════════════════ 🎯 TWO MODES OF OPERATION ═══════════════════════════════════════════════════════════════

Mode 1: Search by topic (default) build_research_timeline(topic="remimazolam")

Mode 2: Build from specific PMIDs build_research_timeline(pmids="12345678,23456789", topic="My Timeline")

═══════════════════════════════════════════════════════════════ MILESTONE DETECTION ═══════════════════════════════════════════════════════════════

Automatically detects significant milestones including:

  • First reports and mechanism discoveries

  • Clinical trial phases (Phase 1/2/3/4)

  • FDA/EMA approvals

  • Meta-analyses and systematic reviews

  • Guidelines and consensus statements

  • Safety alerts and label updates

  • High-impact landmark studies

═══════════════════════════════════════════════════════════════ OUTPUT FORMATS (output_format parameter) ═══════════════════════════════════════════════════════════════

  • "text": Human-readable text format (default)

  • "tree": Research lineage tree — branches by sub-topic (NEW)

  • "mermaid": Mermaid timeline (VS Code, GitHub preview)

  • "mindmap": Mermaid mindmap of research branches (NEW)

  • "json": Full JSON data

  • "timeline_js": TimelineJS library format

  • "d3": D3.js visualization format

Args: topic: Research topic (drug name, gene, disease, etc.) Required if pmids not provided. Examples: "remimazolam", "BRCA1", "pembrolizumab melanoma" pmids: Comma-separated PMIDs or "last" for previous search results If provided, builds timeline from these specific articles. Example: "12345678,23456789,34567890" max_events: Maximum number of events to include (default: 30) min_year: Filter articles from this year (optional, topic mode only) max_year: Filter articles until this year (optional, topic mode only) include_all: Include non-milestone articles as generic events output_format: "text", "tree", "mermaid", "mindmap", "json", "json_tree", "timeline_js", or "d3"

Returns: Research timeline with detected milestones in requested format.

Examples: # By topic build_research_timeline(topic="remimazolam", max_events=20) build_research_timeline(topic="CAR-T therapy", min_year=2015, output_format="mermaid")

# By PMIDs
build_research_timeline(pmids="12345678,23456789", topic="Propofol Studies")
build_research_timeline(pmids="last", topic="Previous Search", output_format="json")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNo
pmidsNo
max_eventsNo
min_yearNo
max_yearNo
include_allNo
highlight_landmarksNo
output_formatNotext

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Since no annotations are provided, the description carries full burden. It details two modes, milestone detection, output formats, and parameter effects. It does not discuss side effects or constraints, but it is comprehensive for a read-only tool.

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 lengthy but well-structured with sections, bullet points, and code examples. It is front-loaded with the main purpose and modes. Minor redundancy could be trimmed, but overall it's efficient.

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 the tool's complexity (8 parameters, no annotations, output schema present), the description is very complete. It covers modes, milestones, output formats, and provides multiple examples. It addresses all user needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description thoroughly explains all 8 parameters, including valid values, defaults, and examples. It adds significant meaning beyond the schema, such as the special value 'last' for pmids.

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 builds a research timeline for a topic or specific PMIDs, distinguishing two modes of operation. It uses specific verbs and resources, and the purpose is unambiguous.

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 provides clear guidance on when to use each mode (by topic or by PMIDs) and includes examples. However, it does not explicitly state when not to use this tool or compare it to siblings like compare_timelines.

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/u9401066/pubmed-search-mcp'

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