Skip to main content
Glama
superagents-lab

Search1API MCP Server

by superagents-lab
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Read a web page

crawl
Read-only

Extract the readable title and full text from any public URL by providing the link.

Instructions

Extract the readable title and full text from a public URL supplied by the user or returned by search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic HTTP or HTTPS URL to retrieve

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

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

  1. Changed3 schema fields changedv0.4.0
    • changedInput schema / properties / url / description
      Previous value: -"URL to crawl"New value: +"Public HTTP or HTTPS URL to retrieve"
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "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"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.8

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly, openWorld, and non-destructive behavior. The description adds meaningful context by stating the tool only handles public URLs and that it extracts a readable title and full text, which clarifies scope and likely output shape beyond the annotations alone.

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 a single, efficient sentence that leads with the tool's core behavior and captures the essential use case. Every word earns its place and there is no redundant or misleading filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only tool with output schema available and strong annotations, the description is complete. It states the source of the URL, the public access requirement, and the output concept well enough for an agent to invoke the tool correctly.

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?

The input schema already describes the single `url` parameter with a format and a 'Public HTTP or HTTPS URL' description at 100% coverage. The tool description adds useful source context ('supplied by the user or returned by search') but does not materially extend the parameter 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 states a specific action ('Extract the readable title and full text') and a specific resource ('a public URL'), making it clear this tool retrieves and reads a single page rather than searching for pages. It also implicitly differentiates from sibling discovery tools like search, news, and trending by framing the URL as an input that can come from the user or search results.

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 clearly conveys when to use the tool: given a public URL, either supplied by the user or returned from a search. It does not explicitly list excluded cases or contrast with sibling tools, so it falls short of the explicit 'when-not-to-use' criterion, but the usage context is sufficiently clear.

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