olostep-mcp

Create Map

create_map

Read-onlyIdempotent

Extract a website's URL list without page content, ranking links by search query and filtering with glob patterns to select pages for scraping.

Instructions

Use this when you need the list of URLs on a website, not their content: to see a site's pages, find a section, or pick pages to scrape. Can rank URLs by search_query and filter them with glob patterns. Returns URLs only. To get the content of many pages from the site, use create_crawl.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_map"
  }
}

Input Schema

Name	Required	Description
`url`	No	Website URL to extract links from.
`top_n`	No	Optional limit for number of URLs returned.
`website_url`	No	Alias for `url`.
`search_query`	No	Optional search query to filter URLs (e.g., "blog").
`exclude_url_patterns`	No	Optional glob patterns to exclude (e.g., "/admin/**").
`include_url_patterns`	No	Optional glob patterns to include (e.g., "/blog/**").

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.21Nov 13, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / url

Added value: +{
+  "description": "Website URL to extract links from.",
+  "format": "uri",
+  "type": "string"
+}

changedInput schema / properties / website_url / description

Previous value: -"Website URL to extract links from."New value: +"Alias for `url`."

removedInput schema / required
```
Removed value: -[
-  "website_url"
-]
```

Addedv1.0.0Jan 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish read-only, open-world, idempotent, and non-destructive behavior. The description adds useful context that it returns URLs only and can rank/filter them, though it does not discuss rate limits, authentication, or pagination.

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 concise and front-loaded: it opens with the core use case, then adds filtering/ranking behavior, the return scope, and the alternative tool. Every sentence contributes useful information.

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 read-only URL-discovery tool with full schema descriptions and no output schema, the description is largely complete. It states the return type and the key behavioral distinction from crawling, though it could clarify parameter aliases and whether the URL is required.

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%, so the schema already documents all six parameters. The description adds some meaning by mentioning search_query and glob filtering, but does not explain the url/website_url alias or top_n behavior beyond what the schema provides.

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 purpose: retrieve the list of URLs on a website rather than their content, with concrete use cases such as seeing a site's pages, finding a section, or picking pages to scrape. It also distinguishes this from create_crawl, which is for page content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use this tool ('need the list of URLs on a website, not their content') and names the alternative for content retrieval: create_crawl. The use-case examples further clarify appropriate selection.

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

Deploy Server