Perplexity Web MCP

Overview Schema Source Related Servers Discussions Admin

pplx_connectors

Retrieve account connector source IDs from the Perplexity rate-limit API and pass them as source_focus to focus queries on specific connected sources.

Instructions

List account connector source IDs that can be passed as source_focus.

Returns source IDs from the Perplexity rate-limit API. Use these IDs as source_focus values, for example source_focus="pitchbook_mcp_cashmere".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pplx_connectors"
  }
}

Input Schema

Name	Required	Description	Default
`refresh`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.14.0Jul 4, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses it 'Returns source IDs from the Perplexity rate-limit API' and explains output usage. Good transparency for a read-only listing tool.

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 efficient sentences: first states action, second provides an example. No wasted words, front-loaded with key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Explains output and usage, but missing explanation of the 'refresh' parameter. With only one parameter, this gap reduces completeness despite existing output schema.

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

Parameters2/5

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

Schema has one parameter 'refresh' with 0% description coverage, yet the description does not explain it. This leaves the agent guessing about its behavior, failing to add meaning beyond the schema.

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 'List account connector source IDs' with a specific verb and resource, and explains the purpose (to be used as source_focus). It distinguishes from siblings by focusing on connector source ID listing.

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?

Provides clear context for use (obtain source_focus values) with an example, but lacks explicit guidance on when not to use or alternatives among sibling tools.

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