Skip to main content
Glama
String AI Web Access MCP Server

String AI Web Access MCP Server

Official

Start a quoted crawl

web_access_sitemap_start

Start the billed crawl approved via a quote, fetching pages within the capped budget. Returns the jobId and status so you can poll progress until the crawl completes.

Instructions

Start a crawl that web_access_sitemap_quote quoted. This is the billing-consent step: pages are billed as they are fetched, capped by the quote or budgetUsd. Call it only after the user has approved the quote's estimatedCostUsd.

Requires jobId. Fails with status 402 if the account balance cannot cover the quote; a 409 partial_state error means an earlier start was interrupted — just call this tool again. A 404 means the job doesn't exist or belongs to another account.

Returns: the jobId and its new status.

Next: poll web_access_sitemap_status until the job is terminal; the terminal response carries its URLs.

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_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe jobId web_access_sitemap_quote returned.

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 annotations (readOnlyHint=false, openWorldHint=true), the description discloses the billing model (pages billed as fetched, capped by the quote or budgetUsd) and enumerates failure semantics: 402 for insufficient balance, 409 partial_state meaning retry by calling again, 404 for missing/foreign jobs. It also notes the return values and the expected next call, none of which the annotations 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?

Front-loaded with purpose and consent gate, then prerequisites, error cases, returns, and next step under bold labels. Each sentence carries distinct operational 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 single-parameter mutating start tool with no output schema, the description supplies the preconditions, the cost model, the retry rule for 409, error meanings, and what is returned. Nothing needed to invoke it correctly or recover from failure 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 real meaning beyond it: jobId must come from the quote tool, and a 404 specifically means the job does not exist or belongs to another account. That extra interpretation of the single parameter's failure mode justifies the bump.

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 first sentence names a specific verb and resource ('Start a crawl') and anchors it to the sibling that produced the input ('that web_access_sitemap_quote quoted'), making it clearly distinct from quote and status. An agent can separate this from the other sitemap tools without opening a 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 states the gating condition explicitly: call only after the user has approved the quote's `estimatedCostUsd`, framed as a billing-consent step. It also names the follow-up tool (web_access_sitemap_status) with the polling condition, so both entry and exit paths are specified.

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