Skip to main content
Glama
cyanheads

clinicaltrialsgov-mcp-server

Clinicaltrials Search Studies

clinicaltrials_search_studies
Read-onlyIdempotent

Search ClinicalTrials.gov for medical studies by condition, intervention, or location. Filter results by recruitment status, trial phase, and geography, select specific data fields to reduce payload size, and paginate through matches.

Instructions

Search for clinical trial studies from ClinicalTrials.gov. Supports full-text and field-specific queries, status/phase/geographic filters, pagination, sorting, and field selection. Use the fields parameter to reduce payload size — full study records are ~70KB each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoGeneral full-text search across all fields.
conditionQueryNoCondition/disease-specific search. E.g., "Type 2 Diabetes", "non-small cell lung cancer".
interventionQueryNoIntervention/treatment search. E.g., "pembrolizumab", "cognitive behavioral therapy".
locationQueryNoLocation search — city, state, country, or facility name.
sponsorQueryNoSponsor/collaborator name search.
titleQueryNoSearch within study titles and acronyms only.
outcomeQueryNoSearch within outcome measure fields.
statusFilterNoFilter by study status. Values: RECRUITING, COMPLETED, ACTIVE_NOT_RECRUITING, NOT_YET_RECRUITING, ENROLLING_BY_INVITATION, SUSPENDED, TERMINATED, WITHDRAWN, UNKNOWN, WITHHELD, NO_LONGER_AVAILABLE, AVAILABLE, APPROVED_FOR_MARKETING, TEMPORARILY_NOT_AVAILABLE.
phaseFilterNoFilter by trial phase. Values: EARLY_PHASE1, PHASE1, PHASE2, PHASE3, PHASE4, NA.
advancedFilterNoAdvanced filter using AREA[] Essie syntax. E.g., "AREA[StudyType]INTERVENTIONAL", "AREA[EnrollmentCount]RANGE[100, 1000]". Combine with AND/OR/NOT and parentheses.
geoFilterNoGeographic proximity filter. Format: distance(lat,lon,radius). E.g., "distance(47.6062,-122.3321,50mi)" for studies within 50 miles of Seattle.
nctIdsNoFilter to specific NCT IDs for batch lookups.
fieldsNoFields to return (PascalCase piece names). Strongly recommended to reduce payload. Common: NCTId, BriefTitle, OverallStatus, Phase, LeadSponsorName, Condition, InterventionName, BriefSummary, EnrollmentCount, StartDate.
sortNoSort order. Format: FieldName:asc or FieldName:desc. E.g., "LastUpdatePostDate:desc", "EnrollmentCount:desc". Max 2 fields comma-separated.
pageSizeNoResults per page, 1–200.
pageTokenNoPagination cursor from a previous response.
countTotalNoInclude total study count in response. Only computed on the first page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
studiesYesMatching studies.
totalCountNoTotal matching studies (first page only when countTotal=true).
nextPageTokenNoToken for the next page. Absent on last page.
searchCriteriaNoEcho of query/filter criteria used. Present when results are empty.
noMatchHintsNoSuggestions for broadening the search when no results are found.
Behavior4/5

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

Annotations cover read-only/idempotent status. Description adds valuable behavioral context not in annotations: specific payload size warning (~70KB per record) implying bandwidth/memory considerations. Also notes pagination and sorting capabilities. Does not mention rate limits or auth requirements.

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 tightly constructed sentences. First sentence front-loads the core purpose and capability summary. Second sentence delivers a critical performance optimization tip. No redundant or wasted words; every clause earns its place.

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?

For a 17-parameter search tool with 100% schema coverage and output schema present, description provides adequate context: identifies data source, explains query flexibility, and highlights the critical payload size constraint. Could enhance by mentioning NCT ID lookup capability or advanced filter syntax specifics, but sufficient given structured data richness.

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%, establishing baseline 3. Description adds meaningful semantic context for the 'fields' parameter (explaining WHY to use it—to reduce payload size—rather than just WHAT it does). Also maps capabilities to parameter groups (full-text, field-specific, geographic) providing mental model.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific action (Search) and resource (clinical trial studies from ClinicalTrials.gov) clearly. Lists key capabilities (full-text, field-specific, filters, pagination). Lacks explicit differentiation from siblings like get_study_record or find_eligible, though the scope is inferable from the description.

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?

Provides specific guidance on using the 'fields' parameter to manage payload size (~70KB per record), which helps optimization decisions. However, lacks broader guidance on when to use this vs. siblings (e.g., get_study_record for single records, get_study_count for counts only) or prerequisites.

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

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