Skip to main content
Glama
superagents-lab

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
NameRequiredDescriptionDefault
queryYesShort, focused search query
time_rangeNoOptional recency window for time-sensitive searches
max_resultsNoMaximum number of results to return
crawl_resultsNoNumber of top results to retrieve as full pages. Each successful page retrieval adds 1 credit to the base 1-credit search request
exclude_sitesNoDomains to exclude from the search
include_sitesNoDomains to include when the user explicitly scopes the search
search_serviceNoSearch engine to use; choose one only when it matches the user's source intentgoogle

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover read-only, non-destructive, open-world behavior. The description adds that results are citable snippets and that full pages require crawl, which is useful context. It does not disclose rate limits, pagination behavior, or edge cases, so it adds only modest behavioral value beyond 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?

The description is two focused sentences that lead with the tool's core purpose, state the return shape, and point to the correct sibling for full-page retrieval. Every sentence contributes value with no wasted words.

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 a rich input schema, output schema, and annotations, the description is largely complete for agent use. The only meaningful gap is the lack of explicit routing among news, trending, and general web search, but the stated use cases cover most practical scenarios.

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 enums and defaults. The description adds no parameter-specific meaning beyond what the schema already provides, which matches the baseline for high schema coverage.

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 clearly states the tool searches the live public web and returns citable results with specific fields. It also references the crawl sibling to signal that full-page retrieval is a separate action. However, it does not explicitly differentiate itself from news or trending, so it is not a full 5.

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?

The description gives explicit usage context: use when the user needs current information, sources, or research. It also routes follow-up full-page extraction to crawl. It lacks explicit 'when not to use' guidance or a direct comparison with news and trending, so it falls short of full guidance.

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