Skip to main content
Glama
superagents-lab

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
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. Dates show when Glama detected each change.

  1. 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"
      +}
  2. 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"
  3. First observedv0.1.8

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, openWorldHint, destructiveHint), the description adds that crawl_results incur an additional credit cost per successful retrieval, a behavioral detail not in annotations. It also describes return fields.

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 concise sentences: the first states purpose and when to use, the second describes output. No wasted words, front-loaded with key information.

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?

Given the tool's complexity (7 params, 1 required) and presence of output schema, the description covers core purpose, output format, and a key behavioral aspect (credit cost). It could mention the default search engine or max_results default, but the schema covers these.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the description adds value by explaining the credit cost for crawl_results, which is not in the schema. It also clarifies the optional extracted text relates to crawling. This goes beyond the schema's parameter descriptions.

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 states 'Search current news' and specifies returning articles with title, URL, snippet, and optional text. It clearly identifies the resource (current news) and action (search), but does not explicitly differentiate from sibling tools like 'trending' or 'search'.

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 says 'when the user asks about recent events, announcements, or coverage', giving context for use. However, it does not mention when not to use this tool or explicitly compare with alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/superagents-lab/search1api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server