Search1API MCP Server

Search the web

search

Read-only

Find current information, sources, and research on the live public web. Get citable results with titles, URLs, and text; crawl any result URL to retrieve the full page.

Instructions

Search the live public web when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text. Pass a result URL to crawl to retrieve the full page.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.

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

A4.2/5.0

Behavior4/5

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

Annotations already mark readOnlyHint, openWorldHint, and destructiveHint, so the bar is lower. The description adds valuable context: it searches the live public web, returns citable results with specific fields, and signals that full-page retrieval is a separate step. This meaningfully supplements the annotations.

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?

Three sentences with no wasted content. The purpose is front-loaded, the return shape is stated, and the follow-up routing to crawl is included efficiently. Every sentence earns its place.

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 a 7-parameter tool with a full output schema and safety annotations, the description covers the core purpose, result format, and relationship to the crawl tool. It does not mention other sibling distinctions, but the rich schema and annotations fill most gaps.

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 baseline is 3 and the description need not elaborate. The description does not add much parameter-specific meaning beyond the schema, which is acceptable given the schema's completeness.

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?

States a specific verb ('Search the live public web'), the resource, and the trigger condition ('when the user needs current information, sources, or research'). It also distinguishes from the sibling crawl tool by explaining that full page retrieval happens via passing a result URL to crawl.

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 when to use the tool and mentions the crawl sibling for page retrieval. However, it does not explicitly contrast with news, sitemap, or trending, so the agent must infer those alternatives from names rather than guidance.

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

Deploy Server