Parallel Search MCP

by L-Chris

Overview Schema Source Related Servers Discussions Admin

JavaScript

Parallel Search with selectable mode

parallel_search

Read-onlyIdempotent

Define a search objective and run multiple web queries with date/domain filters to extract targeted excerpts.

Instructions

Search the web through Parallel Search API. Defaults to turbo; select basic or advanced when needed.

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": {
      "search_queries": "<search_queries>"
    },
    "name": "parallel_search"
  }
}

Input Schema

Name	Required	Description
`mode`	No	Explicit mode override. When omitted, Chinese uses basic and other languages use turbo.
`objective`	No	Self-contained natural-language goal that explains what the search should answer.
`after_date`	No	Only include content published on or after this YYYY-MM-DD date.
`session_id`	No
`max_results`	No
`search_queries`	Yes	Concise keyword queries; 2-3 queries of 3-6 words usually work best.
`exclude_domains`	No
`include_domains`	No
`max_chars_total`	No	Total excerpt/output character limit; defaults to 25,000.

Output Schema

Name	Required	Description	Default
`mode`	Yes
`usage`	Yes
`results`	Yes
`warnings`	Yes
`search_id`	Yes
`session_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds mode selection context, but it also makes a misleading claim: 'Defaults to turbo' whereas the schema explicitly states that Chinese uses basic when mode is omitted. This inaccuracy reduces transparency and could mislead an agent, plus no other behavioral traits (rate limits, pagination) are disclosed.

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 two sentences and extremely concise, front-loading the purpose and then providing mode guidance. Every word earns its place with no filler or redundant 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?

Given the presence of a rich input schema, annotations, and an output schema, the description is adequate but not complete. It clearly states the tool is for web search, but it fails to clarify the language-dependent default behavior (contradicting the schema), and does not mention how this tool relates to parallel_fetch. The gaps are notable but not severe because the schema covers most operational details.

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 description coverage is 56%, but the tool description adds minimal value beyond the schema. It mentions mode names ('turbo', 'basic', 'advanced') and a default, but these are already documented in the mode parameter. Undocumented parameters like session_id, max_results, exclude_domains, and include_domains receive no clarification from the description, so it does not compensate for the coverage gap.

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 identifies the tool's purpose: 'Search the web through Parallel Search API.' This is a specific verb+resource pairing that makes the primary function obvious. It does not explicitly distinguish itself from the sibling tool parallel_fetch, but the word 'Search' versus 'fetch' implies a distinction.

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 some usage context by explaining the default mode and suggesting to 'select basic or advanced when needed.' However, it gives no explicit guidance on when to use this tool versus the sibling parallel_fetch, nor does it mention any exclusions or prerequisites. The usage context is implied but not fully developed.

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

Deploy Server