Search1API MCP Server

Web search

search

Read-only

Find live web information, sources, and research. Returns citable results with title, URL, and text.

Instructions

Search the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Each result includes a URL that can be read in full.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Results page to fetch; only bing, bingcn, baidu, and grokipedia paginate, other engines ignore it
`query`	Yes	Short, focused search query
`time_range`	No	Optional recency window for time-sensitive searches
`max_results`	No	Maximum number of results to return
`crawl_results`	No	Number of top results to retrieve as full pages. Each successful page retrieval adds 1 credit to the base 1-credit search request
`exclude_sites`	No	Domains to exclude from the search
`include_sites`	No	Domains to include when the user explicitly scopes the search
`search_service`	No	Search engine to use; choose one only when it matches the user's source intent	google

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.8.0Oct 14, 2026

addedInput schema / properties / page

Added value: +{
+  "default": 1,
+  "description": "Results page to fetch; only bing, bingcn, baidu, and grokipedia paginate, other engines ignore it",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "number"
+}

changedInput schema / properties / search_service / enum

Previous value: -[
-  "google",
-  "bing",
-  "duckduckgo",
-  "yahoo",
-  "x",
-  "reddit",
-  "github",
-  "youtube",
-  "arxiv",
-  "wechat",
-  "bilibili",
-  "imdb",
-  "wikipedia"
-]New value: +[
+  "google",
+  "bing",
+  "bingcn",
+  "duckduckgo",
+  "yahoo",
+  "yandex",
+  "x",
+  "reddit",
+  "github",
+  "youtube",
+  "arxiv",
+  "wechat",
+  "bilibili",
+  "imdb",
+  "wikipedia",
+  "grokipedia"
+]

changedInput schema / properties / time_range / enum

Previous value: -[
-  "day",
-  "month",
-  "year"
-]New value: +[
+  "day",
+  "week",
+  "month",
+  "year"
+]

Changed10 schema fields changedv0.4.0Jul 29, 2026

changedInput schema / properties / crawl_results / description

Previous value: -"Number of top results to crawl for full webpage content. Each successfully crawled page adds 1 credit to the base 1-credit search request"New value: +"Number of top results to retrieve as full pages. Each successful page retrieval adds 1 credit to the base 1-credit search request"

addedInput schema / properties / crawl_results / minimum
```
Added value: +0
```

changedInput schema / properties / exclude_sites / description

Previous value: -"List of sites to exclude from search. Only use when you need to explicitly filter out specific domains from results"New value: +"Domains to exclude from the search"

changedInput schema / properties / include_sites / description

Previous value: -"List of sites to include in search. Only use when you need special results from sites not available in search_service"New value: +"Domains to include when the user explicitly scopes the search"

addedInput schema / properties / max_results / maximum
```
Added value: +50
```
addedInput schema / properties / max_results / minimum
```
Added value: +1
```

changedInput schema / properties / query / description

Previous value: -"Search query, be simple and concise"New value: +"Short, focused search query"

changedInput schema / properties / search_service / description

Previous value: -"Specify the search engine to use. Choose based on your specific needs"New value: +"Search engine to use; choose one only when it matches the user's source intent"

changedInput schema / properties / time_range / description

Previous value: -"Time range for search results, only use when specific time constraints are required"New value: +"Optional recency window for time-sensitive searches"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Stable identifier for this result; for web results this is the canonical URL",
+            "type": "string"
+          },
+          "metadata": {
+            "additionalProperties": true,
+            "description": "Additional source metadata",
+            "type": "object"
+          },
+          "text": {
+            "description": "Result snippet or extracted page text when available",
+            "type": "string"
+          },
+          "title": {
+            "description": "Human-readable result title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Canonical URL that clients can cite and users can open",
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.3.1Jul 28, 2026

changedInput schema / properties / crawl_results / description

Previous value: -"Number of results to crawl for full webpage content, useful when search result summaries are insufficient for complex queries"New value: +"Number of top results to crawl for full webpage content. Each successfully crawled page adds 1 credit to the base 1-credit search request"

First observedv0.1.8May 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds the result shape (id, title, URL, text) and the read-in-full affordance, but that overlaps with the existing output schema and omits operational context such as the per-crawl credit cost that the schema notes. Additive value beyond structured fields is modest.

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?

Three short sentences, front-loaded with the purpose before the return details. Tight overall, though the final sentence ('Each result includes a URL that can be read in full') is largely redundant with the preceding description of result fields.

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?

For an 8-parameter tool with full schema coverage, an output schema, and rich annotations, the description delivers a clear purpose and return summary. Guidance on engine selection tradeoffs is left to the schema, which is acceptable given the structured fields cover it.

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 8 parameters — including the pagination caveat for specific engines and the credit cost of crawl_results — are already documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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+resource ('Search the live public web') and the information need it serves ('current information, sources, or research'), clearly distinguishing it from a plain lookup. It does not explicitly name siblings like news, trending, or crawl, so an agent must infer the boundary between general search and those specialized tools.

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?

Gives a clear use context — when the user needs current information, sources, or research — which is exactly the trigger condition for a search tool. It stops short of naming alternatives (news, trending, crawl) or stating when-not to use it, but the positive guidance is unambiguous.

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

Deploy Server