Skip to main content
Glama
jujubytes-a11y

Perplexity MCP Server

perplexity_search

Search the web, academic papers, or SEC filings using Perplexity Sonar models. Filter results by recency, domain, or date range for focused answers with citations.

Instructions

General web search via Perplexity Sonar (default model: sonar-pro).

Returns JSON with answer, citations, and optional search_results/usage.

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-pro
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 are provided, so the description carries the full burden. It discloses return format and filter behaviors but does not mention rate limits, authentication, or potential side effects. Adequate but not comprehensive.

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?

Well-structured with front-loaded purpose, return format, and bullet-point filter guidelines. No unnecessary sentences; every part adds value.

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 9 parameters, 100% schema coverage, and existing output schema, the description covers essential aspects. Could mention authentication or rate limits, but not critical for correct invocation.

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%, baseline 3. Description adds practical usage guidance beyond schema descriptions, such as when to use recency vs date filters and domain filter modes.

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 is a general web search via Perplexity Sonar, returns JSON with answer and citations. The name and description distinguish it from sibling 'perplexity_deep_research'.

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 detailed guidance on when to use each optional filter, but does not explicitly compare this tool with the sibling deep research tool. Usage context is implied for general search.

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