Skip to main content
Glama
Sign In
Search1API MCP Server

Search1API MCP Server

by superagents-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Web search

search
Read-only

Search the live web via Google, Bing, DuckDuckGo, Yahoo, or specialized sources like GitHub, Reddit, and arXiv to find current information, sources, and citable results.

Instructions

Search the live web through one chosen engine: Google, Bing, DuckDuckGo, or Yahoo for the open web, or a specialized source such as GitHub, Reddit, X, YouTube, arXiv, Wikipedia, WeChat, or Bilibili when the user wants results from that platform. Use when the user needs current information, sources, or research. Returns citable results with id, title, URL, and text; read any URL in full with crawl.

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to fetch when the first page was not enough; only bing, bingcn, and grokipedia paginate, other engines ignore it
queryYesShort, focused search query
time_rangeNoRestrict results to those published recently, for time-sensitive questions; leave unset for evergreen topics
max_resultsNoHow many sources the answer needs; a handful suits most questions, more suits a broad survey
crawl_resultsNoHow many top results to also read in full, so their text holds the whole page instead of a snippet. 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

NameRequiredDescriptionDefault
resultsYesMatching sources, most relevant first; read any url in full with crawl

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.9.0
    • changedInput schema / properties / crawl_results / description
      Previous value: -"Number of top results to retrieve as full pages. Each successful page retrieval adds 1 credit to the base 1-credit search request"New value: +"How many top results to also read in full, so their text holds the whole page instead of a snippet. Each successful page retrieval adds 1 credit to the base 1-credit search request"
    • changedInput schema / properties / max_results / description
      Previous value: -"Maximum number of results to return"New value: +"How many sources the answer needs; a handful suits most questions, more suits a broad survey"
    • changedInput schema / properties / page / description
      Previous value: -"Results page to fetch; only bing, bingcn, baidu, and grokipedia paginate, other engines ignore it"New value: +"Which page of results to fetch when the first page was not enough; only bing, bingcn, and grokipedia paginate, other engines ignore it"
    • changedInput schema / properties / time_range / description
      Previous value: -"Optional recency window for time-sensitive searches"New value: +"Restrict results to those published recently, for time-sensitive questions; leave unset for evergreen topics"
    • addedOutput schema / properties / results / description
      Added value: +"Matching sources, most relevant first; read any url in full with crawl"
  2. Changed3 schema fields changedv0.8.0
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Results page to fetch; only bing, bingcn, baidu, and grokipedia paginate, other engines ignore it",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "number"
+}
    • changedInput schema / properties / search_service / enum
      Previous value: -[
-  "google",
-  "bing",
-  "duckduckgo",
-  "yahoo",
-  "x",
-  "reddit",
-  "github",
-  "youtube",
-  "arxiv",
-  "wechat",
-  "bilibili",
-  "imdb",
-  "wikipedia"
-]New value: +[
+  "google",
+  "bing",
+  "bingcn",
+  "duckduckgo",
+  "yahoo",
+  "yandex",
+  "x",
+  "reddit",
+  "github",
+  "youtube",
+  "arxiv",
+  "wechat",
+  "bilibili",
+  "imdb",
+  "wikipedia",
+  "grokipedia"
+]
    • changedInput schema / properties / time_range / enum
      Previous value: -[
-  "day",
-  "month",
-  "year"
-]New value: +[
+  "day",
+  "week",
+  "month",
+  "year"
+]
  3. 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"
+}
  4. 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"
  5. First observedv0.1.8

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint=false, and destructiveHint=false, so the safety and side-effect profile is covered before the description is read. The description adds modest context ("live web", citable results, crawl for full text) but says nothing about credit costs, rate limits, or per-engine reliability — the credit note appears only in the crawl_results param description.

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, no padding: the capability and engine scope come first, then the usage trigger, then the return shape and follow-up action. The long engine list in sentence one is dense but functional, and nothing repeats what the annotations already state.

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 an output schema present and 100% param coverage, the description only needs to convey purpose, trigger, and routing, all of which it does. Minor gaps remain around pagination caveats (only some engines paginate) and cost, but those live in the schema and are not required in the description.

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 every parameter already carries its own explanation, establishing a baseline of 3. The description's engine enumeration overlaps the search_service enum and is actually less complete (omits yandex, imdb, bingcn, grokipedia), adding no syntax or selection heuristics 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?

States a specific verb and resource ("Search the live web") and enumerates the engine scope, including specialized platforms like GitHub, Reddit, and arXiv. It also explicitly hands off full-page reading to the sibling tool crawl, so the agent can tell this apart from crawl without opening either schema.

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?

"Use when the user needs current information, sources, or research" gives a clear triggering condition, and the mention of crawl establishes the read-in-full alternative. It stops short of naming when-not-to-use cases or contrasting with siblings like news or trending, which likely overlap for time-sensitive queries.

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