Skip to main content
Glama
String AI Web Access MCP Server

String AI Web Access MCP Server

Official

Check a crawl and read its URLs

web_access_sitemap_status
Read-onlyIdempotent

Poll a sitemap crawl job until it finishes and get the discovered URLs, with paging to retrieve each batch of found pages.

Instructions

Poll a crawl job until it is terminal; the terminal response also carries the URLs it discovered. Statuses: awaiting_approval → running → terminal completed | failed | canceled | token_cap_exceeded (budget hit before maxPages; collected results are still readable). While running it returns pending and processed counts and no URLs; a partial_state status means an interrupted start — call web_access_sitemap_start again to repair it. Poll every few seconds for small crawls; give hundreds-of-pages crawls tens of seconds between polls.

Once the job is terminal, the response carries total and urls, one page of the discovered URLs. Optional limit (1–5000, default 1000) and offset (≥ 0) choose the page; out-of-range values are rejected. Each entry has url, statusCode (0 = discovered but not fetched), depth, parentUrl, isSitemap, sourceType, and an error when that page failed. discoveredUrls (links found on the page) is only present for ~1h after completion; afterwards results come from durable storage which omits it — everything else stays available.

Requires jobId. A 404 means the job doesn't exist or belongs to another account. If the job is terminal but its URLs cannot be read, the call fails rather than return the status without them; call it again.

Returns: the jobId and status, with pending, processed, pagesProcessed, estimatedCostUsd, errorMessage and finishedAt as the job reports them, and total and urls once it is terminal.

Next: call again with offset advanced by the page size until it reaches total; read a page's content with web_access_fetch.

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": {
      "jobId": "<jobId>"
    },
    "name": "web_access_sitemap_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe jobId web_access_sitemap_quote returned.
limitNoOnce the job is terminal: URLs per page, 1-5000 (default 1000).
offsetNoOnce the job is terminal: number of URLs to skip for pagination (0 or more).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare it a safe idempotent read; the description adds the full status lifecycle (awaiting_approval → running → completed/failed/canceled/token_cap_exceeded), that budget-exceeded results remain readable, that URLs are absent while running, the ~1h expiry of `discoveredUrls`, the 404 account-scoping meaning, and the fail-rather-than-return-partial behavior.

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?

Dense but organized into lifecycle, paging, access rules, returns, and next steps, with the terminal-status payoff front-loaded. The `**Returns:**` paragraph restates field information already given earlier, which costs a little efficiency in an otherwise tight definition.

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?

There is no output schema, so the description carries the return contract itself and does so fully: jobId, status, progress counters, cost, error fields, and the per-URL entry shape with statusCode=0 and error semantics. Nothing an agent needs to call or page through results 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 schema already documents all three parameters; the description still adds operational meaning — limit/offset only take effect once the job is terminal and out-of-range values are rejected. It does not add format details beyond that, which is acceptable given the schema.

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?

First sentence states a specific verb and resource (poll a crawl job, return discovered URLs) and marks the terminal behavior that distinguishes it from web_access_sitemap_start. An agent can tell exactly what it gets back without opening the 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?

Gives explicit polling cadence (every few seconds for small crawls, tens of seconds for hundreds of pages), the re-call-to-repair rule for `partial_state`, the offset-advancement loop, and names web_access_fetch for reading page content. Both when-to-use and what-to-do-next are stated.

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