Skip to main content
Glama
String AI Web Access MCP Server

String AI Web Access MCP Server

Official

Quote a site crawl

web_access_sitemap_quote

Quote an asynchronous same-domain crawl of authorized public pages to estimate cost and discover pages for audits or coverage checks; no crawl runs until approval.

Instructions

Quote an asynchronous crawl of authorized public pages on one website. Nothing is crawled or billed: the quote creates a job that waits for approval. Starting from one URL, the crawler follows same-domain links breadth-first and can also seed from the site's /sitemap.xml. Requests must comply with destination policy, robots directives, rate limits, and access controls.

Use it to discover pages for site audits, authorized retrieval worklists, or coverage checks before fetching individual pages. Not for: reading one page's content (use web_access_fetch) or open-ended web queries (use web_access_search).

Requires url. Optional: maxPages (1–10000, default 10), maxDepth (1–100, default 2), pathPrefix (only crawl URLs whose path starts with this, e.g. "/docs"), budgetUsd (spend ceiling; the crawl stops with status token_cap_exceeded if it would exceed it), useSitemap (also seed the site's root /sitemap.xml — one extra billed page, but finds pages links miss).

{ "url": "https://example.com", "maxPages": 200, "maxDepth": 3 }

Returns: jobId, estimatedPages, and estimatedCostUsd, with status awaiting_approval. A 403 means the target domain is blocked for this account; contact String support.

Next: show the user estimatedCostUsd. Only once they approve that cost, call web_access_sitemap_start with the jobId.

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": "web_access_sitemap_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full http(s) URL to start crawling from. The crawl stays on this URL's domain.
maxDepthNoMaximum link depth from the start URL, 1-100 (server default 2).
maxPagesNoMaximum pages to fetch, 1-10000 (server default 10). Each fetched page is billed once the crawl starts.
budgetUsdNoSpend ceiling in USD (min 0.0001). The crawl finalizes as token_cap_exceeded when it would exceed this; omit to let the approved quote be the cap.
pathPrefixNoRestrict the crawl to URLs whose path starts with this prefix, e.g. '/docs'.
useSitemapNoAlso seed the crawl from the site's root /sitemap.xml (one extra billed page; finds pages that internal links miss).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (which only say non-read-only, open-world, non-idempotent), the description discloses that nothing is crawled or billed at quote time, that a job is created in awaiting_approval, that crawling is breadth-first within one domain, that policy/robots/rate-limit/access rules apply, that budget overruns finalize as token_cap_exceeded, and that a 403 means the domain is account-blocked. This is substantive behavioral context the annotations cannot convey.

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 definition is front-loaded with purpose, then structured into 'Not for', required/optional params, a minimal JSON example, 'Returns', and 'Next'. Despite its length, each block carries decision-relevant information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter job-creating tool with no output schema, the description covers inputs, side effects, return values (jobId, estimatedPages, estimatedCostUsd), error semantics (403), and the required next step. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: it restates the defaults (maxPages 10, maxDepth 2), explains pathPrefix with a concrete '/docs' example, clarifies budgetUsd acts as a spend ceiling with a named terminal status, and notes useSitemap costs one extra billed page. These add operational nuance beyond the field definitions.

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 opens with a specific verb and resource — 'Quote an asynchronous crawl of authorized public pages on one website' — and immediately clarifies the quote/no-crawl distinction. An agent can distinguish this from web_access_fetch, web_access_search, and web_access_sitemap_start without opening any schema.

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 gives explicit positive cases (site audits, retrieval worklists, coverage checks) and an explicit 'Not for' section routing to web_access_fetch for single pages and web_access_search for open-ended queries. It also states the follow-up step: only after cost approval, call web_access_sitemap_start with the jobId.

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