Perplexity MCP Server

perplexity_search_web

Search the web via Perplexity AI with recency filters to retrieve current, citation-backed answers for time-sensitive queries.

Instructions

Search the web using Perplexity AI with recency filtering

Input Schema

TableJSON Schema

Name	Required	Description	Default
`model`	No	The name of the model to use for generating completions. Options include sonar, sonar-pro, and other models listed at https://docs.perplexity.ai/guides/model-cards
`query`	Yes	Search query
`top_k`	No	Limits the number of high-probability tokens to consider for generation. Set to 0 to disable.
`top_p`	No	Nucleus sampling threshold, controlling the token selection pool based on cumulative probability.
`stream`	No	Whether to stream the response incrementally using server-sent events.
`recency`	No	Filter results by recency	month
`max_tokens`	No	The maximum number of tokens to generate. Sum of max_tokens and prompt tokens should not exceed the model's context window limit.
`temperature`	No	Controls generation randomness, with 0 being deterministic and values approaching 2 being more random.
`return_images`	No	Whether to include images in the model's response.
`presence_penalty`	No	Penalty for new tokens based on their current presence in the text, encouraging topic variety. Mutually exclusive with the frequency_penalty parameter.
`return_citations`	No	Whether to include citations in the model's response.
`frequency_penalty`	No	Multiplicative penalty for new tokens based on their frequency in the text to avoid repetition. Mutually exclusive with the presence_penalty parameter.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Sep 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond purpose. It does not state authentication requirements, rate limits, cost, latency, or the shape of the response (citations, images, streaming), and 'recency filtering' merely restates a schema parameter.

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?

A single front-loaded sentence with zero filler, which is efficient. However, given a 12-parameter tool with no annotations, the extreme brevity leaves too much unsaid rather than being appropriately sized.

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?

For a 12-parameter tool with no annotations and no output schema, the definition does very little work. It never explains output format (citations, images), streaming behavior, or credential requirements that an agent would need to invoke it confidently.

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?

Schema description coverage is 100%, so all 12 parameters are already documented in the schema, making 3 the baseline. The description adds no parameter-level meaning beyond what the schema already provides.

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 a specific verb (Search) and resource (the web) and adds the mechanism (Perplexity AI) plus a modifier (recency filtering). It is clear but there are no sibling tools to differentiate from, so it lands just below the top tier.

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?

Usage is implied by 'Search the web' but there is no explicit when-to-use, when-not-to-use, or alternative tool guidance. Nothing tells the agent when this is preferable to other retrieval approaches.

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

Deploy Server

Other Tools

perplexity_search_webB