Skip to main content
Glama
superagents-lab

Search1API MCP Server

by superagents-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

News search

news
Read-only

Find recent articles when users ask about events, announcements, or coverage. Returns citable results with title, URL, snippet, and optional extracted 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
NameRequiredDescriptionDefault
queryYesShort, focused news query
time_rangeNoOptional recency window; use day for breaking news
max_resultsNoMaximum number of articles to return
crawl_resultsNoNumber of top articles to retrieve as full pages. Each successful retrieval adds 1 credit to the base 1-credit news request
exclude_sitesNoNews domains to exclude
include_sitesNoNews domains to include
search_serviceNoNews search engine to usebing

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / time_range / enum
      Previous value: -[
-  "day",
-  "month",
-  "year"
-]New value: +[
+  "day",
+  "week",
+  "month",
+  "year"
+]
  2. Changed11 schema fields changedv0.4.0
    • 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"
+}
  3. Changed1 schema field changedv0.3.1
    • 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"
  4. First observedv0.1.8

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds that results are "citable" with title/URL/snippet/optional text, but says nothing about cost, freshness guarantees, or rate behavior beyond what the schema's credit note already implies.

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, purpose front-loaded and trigger condition second, with zero filler. Every clause earns its place.

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?

With a rich schema, output schema, and safety annotations, the description covers enough to call the tool. The notable gap is sibling routing: in a toolset containing both `search` and `trending`, the description never explains why an agent should pick `news` over those alternatives.

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 fully documents all seven parameters (including the credit cost of crawl_results and the recency enum). 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 and resource ("Search current news") plus the triggering user intent, so the agent knows this is a news-retrieval tool rather than a general one. However, it never distinguishes itself from the sibling `search` or `trending` tools, leaving ambiguity about which to pick.

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?

"when the user asks about recent events, announcements, or coverage" gives clear, actionable context for when to invoke this tool. There are no exclusions or named alternatives (e.g. no guidance on choosing `trending` for trending topics over `news`), so it stops short of a 5.

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