Skip to main content
Glama
jujubytes-a11y

Perplexity MCP Server

perplexity_deep_research

Synthesizes in-depth research from web, academic, or SEC sources, returning answers with citations and usage data.

Instructions

Comprehensive synthesis via Perplexity Sonar Deep Research.

Returns JSON with answer, citations, and optional search_results/usage.
Uses a longer timeout suitable for exhaustive research.

When to use optional filters:
- search_recency_filter: current events / "latest" questions (hour|day|week|month|year).
- search_after/before_date_filter: absolute windows as MM/DD/YYYY; prefer over recency when exact.
- search_domain_filter: trusted sources (allowlist) or exclude noise (denylist with '-'); one mode only.
- search_mode: 'academic' for papers, 'sec' for SEC filings; omit for general web.
- Leave filters unset for broad evergreen queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoSonar model id: sonar (fast), sonar-pro (default search quality), sonar-deep-research (exhaustive synthesis), or sonar-reasoning-pro. Leave the tool default unless you need a different speed/depth tradeoff.sonar-deep-research
queryYesNatural-language search or research question. Non-empty; max 4000 characters.
max_tokensNoMaximum completion tokens. Omit to use the API default; set only when you need a shorter or longer answer budget.
search_modeNoSearch corpus: 'web' (general web, default), 'academic' (scholarly papers), or 'sec' (SEC filings). Set academic for literature reviews; sec for company filings; omit or web for general questions.
temperatureNoSampling temperature (0-2). Lower values (default 0.2) keep answers focused and factual; raise only when more varied phrasing is wanted.
search_domain_filterNoLimit or exclude domains/URLs (max 20). Allowlist: ['nature.com', 'nih.gov']. Denylist: ['-reddit.com', '-pinterest.com']. Use one mode only - do not mix allowlist and denylist entries in the same request.
search_recency_filterNoRestrict results to recent publications: hour, day, week, month, or year. Use for news, live events, or 'latest' questions. Omit for evergreen topics. Prefer absolute date filters when an exact window is known.
search_after_date_filterNoOnly include results published after this date. Format: MM/DD/YYYY (e.g. 01/15/2024). Prefer over search_recency_filter for an absolute start.
search_before_date_filterNoOnly include results published before this date. Format: MM/DD/YYYY (e.g. 12/31/2024). Prefer over search_recency_filter for an absolute end.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations exist, so the description must carry the burden. It discloses the output format (JSON with answer, citations, optional fields), timeout behavior ('longer timeout suitable for exhaustive research'), and optional filter behavior. However, it does not discuss error states, rate limits, or authentication requirements, which could be important for agent planning.

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 concise, with a clear front-loaded purpose and output format, followed by the timeout note and structured filter guidance. Every sentence adds value. The filter section could be more bulletized, but it remains easy to scan. No redundant or tautological content.

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?

Given the tool's complexity (9 parameters, output schema exists), the description covers the core purpose, output format, timeout, and filter usage comprehensively. It does not need to explain return values since the output schema provides that. Missing details like error handling or limits are acceptable given the parameter and schema 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 description coverage is 100%, so the baseline is 3. The description adds value by connecting filter usage to real-world scenarios (e.g., 'current events / "latest" questions' for recency, 'absolute windows as MM/DD/YYYY' for date filters) and stating preferences (e.g., 'prefer over recency when exact'). This context clarifies when to use each parameter beyond the schema's individual descriptions.

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?

The description clearly states the tool performs 'comprehensive synthesis via Perplexity Sonar Deep Research' and returns JSON with answer and citations. It implies a deeper, more exhaustive research capability compared to the sibling tool 'perplexity_search', though it does not explicitly differentiate. The purpose is specific and actionable.

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 provides detailed guidance on when to use optional filters (e.g., 'search_recency_filter: current events / "latest" questions'), and advises 'Leave filters unset for broad evergreen queries.' However, it lacks explicit guidance on when to choose this tool over the sibling 'perplexity_search,' leaving the AI agent to infer based on the 'deep research' name and 'longer timeout' mention.

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/jujubytes-a11y/mcp_perplexity'

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