Skip to main content
Glama
Sign In
perplexity-pro-mcp

perplexity-pro-mcp

by MIt9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

perplexity_export

Export any Perplexity answer entry to Markdown or PDF for offline use and sharing.

Instructions

Export a Perplexity answer entry as markdown or PDF.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entry_uuid": "<entry_uuid>"
    },
    "name": "perplexity_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoExport formatmd
entry_uuidYesEntry UUID (from perplexity_search result or thread)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 full burden. It fails to disclose behavioral traits such as whether the export is a file download or link, authentication requirements, or rate limits. The description is too minimal for a tool with zero annotation coverage.

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?

The description is a single sentence with no wasted words, efficiently communicating the purpose.

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?

The tool has no output schema, so the description should explain what the output is. It does not specify whether the export returns a file, a URL, or something else. Given simplicity, it is incomplete.

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 the schema already documents both parameters. The description adds no meaning beyond the schema, giving a baseline score of 3.

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 the tool exports a Perplexity answer entry as markdown or PDF, specifying the verb (Export) and resource (Perplexity answer entry). It distinguishes from siblings like perplexity_search (search) and perplexity_threads (list threads) through different actions.

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 implies usage context (after obtaining an entry_uuid from search or thread), but does not explicitly state when to use vs alternatives, nor provides prerequisites or exclusions.

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