Skip to main content
Glama

Map a site's URLs

map_site
Read-onlyIdempotent

Discover and map a site's discoverable URLs from a seed URL, optionally ranking them by relevance to a search phrase.

Instructions

Map a site's discoverable URLs starting from a seed URL. search ranks them by relevance to a phrase.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "map_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
searchNo
dry_runNoNot supported here: leave it out and use the estimate tool to price a call.
optionsNoOther API fields for this operation, merged into the request body as they are (see the Clawifi API docs).
max_urlsNo
timeout_secondsNo
same_domain_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.4.1
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "default": null,
      +  "description": "Not supported here: leave it out and use the estimate tool to price a call.",
      +  "title": "Dry Run"
      +}
    • removedInput schema / properties / kwargs
      Removed value: -{
      -  "title": "Kwargs"
      -}
    • addedInput schema / properties / max_urls
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Max Urls"
      +}
    • addedInput schema / properties / options
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Other API fields for this operation, merged into the request body as they are (see the Clawifi API docs).",
      +  "title": "Options"
      +}
    • addedInput schema / properties / same_domain_only
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Same Domain Only"
      +}
    • addedInput schema / properties / search
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Search"
      +}
    • addedInput schema / properties / timeout_seconds
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Timeout Seconds"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "url",
      -  "kwargs"
      -]New value: +[
      +  "url"
      +]
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), which lowers the burden. The description adds that results are 'discoverable' URLs discovered from a seed and that search reorders rather than filters them, but says nothing about result volume caps, cost, or traversal depth behavior that an agent would want before a potentially expensive open-world call.

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?

Two short sentences, front-loaded with the action and seed input, with zero filler. The second sentence is slightly abrupt and lowercase-initial, reading as a fragment rather than a documented parameter behavior, but nothing is wasted.

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 return values need no explanation, and annotations carry the safety profile. Still, with seven parameters and a low schema coverage, the definition leaves meaningful gaps around scoping, limits, and traversal behavior for an open-world mapping operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is low at 29%, with descriptions only on dry_run and options, so the description needs to compensate. It explains only the search parameter (ranks by relevance to a phrase); url, max_urls, timeout_seconds, and same_domain_only get no treatment, leaving an agent to guess at scope and limit semantics for the remaining parameters.

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 and resource: "Map a site's discoverable URLs starting from a seed URL." That is concrete enough to distinguish it from a plain fetch or extract, but it never names or contrasts a sibling such as crawl, so the differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives like crawl or fetch, even though 'discoverable URLs' overlaps heavily with a crawler. The only usage hint is the implicit seed-URL scoping and the search-ranking aside, which tells the agent nothing about when to pick this over its siblings.

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