Skip to main content
Glama
Sign In
Search1API MCP Server

Search1API MCP Server

by superagents-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read a web page

crawl
Read-only

Read a public web page by URL and return its title, URL, and main text so answers use full page content instead of a search snippet.

Instructions

Read a public web page supplied by the user or returned by search. Returns its title, URL, and main content as text, so you can answer from the full page instead of a snippet.

Input Schema

NameRequiredDescriptionDefault
urlYesAddress of the page to read, such as a link the user shared or a URL from search results

Output Schema

NameRequiredDescriptionDefault
resultYesThe page that was read; text holds its main content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.0
    • changedInput schema / properties / url / description
      Previous value: -"Public HTTP or HTTPS URL to retrieve"New value: +"Address of the page to read, such as a link the user shared or a URL from search results"
    • addedOutput schema / properties / result / description
      Added value: +"The page that was read; text holds its main content"
  2. 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"
+}
  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 declare readOnly, openWorld, non-idempotent, and non-destructive behavior. The description adds that only public pages are read and that the output is the title, URL, and main content as text, but it does not mention limitations such as JavaScript rendering, paywalls, authentication, or 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?

The description is two sentences, front-loads the action, and immediately explains the practical benefit of reading the full page rather than a snippet. There is no redundant or filler text.

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?

For a one-parameter read tool with rich annotations and an output schema, the description covers purpose, source, and output nature adequately. It leaves a small gap around sibling differentiation and runtime limitations, but nothing essential for a basic call is missing.

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 coverage is 100%, and the schema already describes the URL as a link from the user or search results. The description restates that sourcing context but adds no new syntax, format, or constraint details for the parameter.

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 gives a specific verb and resource: reading a public web page. It contrasts the result with a search snippet, which helps distinguish it from the search tool, but it does not explicitly name or rule out close siblings such as render_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?

It clearly states when this tool applies: when the user supplies a URL or when a URL comes from search results. It does not explicitly say when not to use it or which sibling handles alternative cases, so it falls short of full routing guidance.

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