Search1API MCP Server

Discover links on a site

sitemap

Read-only

Discover related public links from a page or domain URL to explore a site's structure and available pages, aiding research, crawling, and content mapping.

Instructions

Discover related public links from a page or domain when the user wants to explore a site's structure or available pages.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	Public page or domain URL whose links should be discovered

Output Schema

TableJSON Schema

Name	Required	Description	Default
`links`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.4.0Jul 29, 2026

changedInput schema / properties / url / description

Previous value: -"URL to get sitemap"New value: +"Public page or domain URL whose links should be discovered"

addedInput schema / properties / url / format
```
Added value: +"uri"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "links": {
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "links"
+  ],
+  "type": "object"
+}

First observedv0.1.8May 8, 2026

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, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds that only public links are surfaced, but says nothing about crawl depth, result limits, or how discovery is scoped — modest added context over 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence combining the action with the trigger condition; no filler. Slight redundancy between 'related public links' and 'available pages' keeps it from being maximally tight.

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-only tool with an output schema and rich annotations, the description supplies the needed intent and scope. Return values need not be explained since an output schema exists; the only gap is disambiguation from the crawl sibling.

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 with 100% schema description coverage, so the schema already documents 'url'. The description's 'page or domain' phrasing reinforces that a domain is acceptable, but adds no format or constraint detail beyond the schema. Baseline 3 applies.

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 (discover) and resource (related public links from a page or domain), and scopes it to public links. It does not explicitly differentiate itself from the sibling 'crawl', which also traverses sites, so an agent must infer the boundary.

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?

Gives a clear selection context: use when the user wants to explore a site's structure or available pages. It stops short of naming the closest alternative (crawl) or stating when not to use it, leaving the sitemap-vs-crawl choice to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server