Skip to main content
Glama
superagents-lab

Search1API MCP Server

by superagents-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read a web page

crawl
Read-only

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

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.

  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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and open-web profile is covered structurally. The description adds that the output is extracted readable text rather than raw markup, plus the public-URL restriction, but says nothing about failure modes (paywalls, JS-rendered content, rate limits).

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?

A single sentence with zero padding; the action and output are front-loaded and the input-sourcing hint is appended without derailing the sentence.

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?

An output schema exists, so the description needn't explain return values, and the single input is fully documented. It is nearly complete for a one-parameter read tool, with the main gap being no guidance on unreadable or dynamically rendered pages.

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?

Only one parameter, and the schema already describes it fully (format: uri, 'Public HTTP or HTTPS URL to retrieve') at 100% coverage, so the baseline is 3. The description reinforces the public-URL constraint and hints at the URL source, but adds no format or validity detail beyond the schema.

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 (extract) and concrete outputs (readable title and full text) from a clearly bounded resource (a public URL). It does not explicitly distinguish itself from siblings like render_results or sitemap, which an agent might plausibly confuse with page retrieval.

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?

'Supplied by the user or returned by search' implies a usage chain after the search tool, which is useful contextual guidance. However, there is no explicit when-not guidance or mention of when a sibling such as render_results (e.g., JS-heavy pages) would be the better choice.

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