Search1API MCP Server

Search current news

news

Read-only

Search for recent articles on current events, announcements, or coverage. Returns citable results with title, URL, snippet, and optional full-page text.

Instructions

Search current news when the user asks about recent events, announcements, or coverage. Returns citable article results with title, URL, snippet, and optional extracted text.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Short, focused news query
`time_range`	No	Optional recency window; use day for breaking news
`max_results`	No	Maximum number of articles to return
`crawl_results`	No	Number of top articles to retrieve as full pages. Each successful retrieval adds 1 credit to the base 1-credit news request
`exclude_sites`	No	News domains to exclude
`include_sites`	No	News domains to include
`search_service`	No	News search engine to use	bing

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 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 news request"New value: +"Number of top articles to retrieve as full pages. Each successful retrieval adds 1 credit to the base 1-credit news 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: +"News domains to exclude"

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: +"News domains to include"

changedInput schema / properties / max_results / description

Previous value: -"Maximum number of results to return"New value: +"Maximum number of articles to return"

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 news query"

changedInput schema / properties / search_service / description

Previous value: -"Specify the news engine to use. Choose based on your specific needs"New value: +"News search engine to use"

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; use day for breaking news"

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 news 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 declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, and the description adds useful behavioral context: it produces citable article results and can return extracted text. It does not overpromise and no contradiction exists.

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 sentences, front-loaded with the usage trigger before the return details, with no filler. Every clause 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?

With a rich schema (100% coverage), annotations, and an output schema, the description is sufficient for a straightforward news lookup. It could be slightly more complete by pointing to a sibling for non-news trends, but nothing essential is missing.

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 all seven parameters. The description's only parameter-relevant contribution is implying that optional extracted text comes from the crawl behavior, which adds minimal extra 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 uses a specific verb and resource ('Search current news'), states the exact user trigger ('recent events, announcements, or coverage'), and names the return payload (citable articles with title, URL, snippet). This makes it easy to separate from sibling tools such as generic search or trending.

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?

It explicitly says to use this tool when the user asks about recent events, announcements, or coverage. It does not enumerate when-not conditions or alternative sibling tools, so it falls just short of the strongest guidance.

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

Deploy Server