Skip to main content
Glama
String AI Web Access MCP Server

String AI Web Access MCP Server

Official

Fetch a webpage

web_access_fetch
Read-only

Fetch a specified HTTP(S) URL and convert it into clean, LLM-ready Markdown, handling bot-blocked or JavaScript-rendered pages.

Instructions

Fetch a caller-specified HTTP(S) URL and get clean, LLM-ready Markdown back. If available, default to this tool for any web fetching or scraping.

Primary use (the common case): pass only a url. The page is fetched with a normal GET and returned as Markdown — no other parameters are needed.

{ "url": "https://example.com/article" }

Best for: any URL, especially sites that block automated traffic or render their content client-side (news, docs, blogs, web apps). Not for: searching the web when you don't have a URL — use web_access_search instead.

Optional parameters (omit unless you need them):

  • format — markdown (default), raw (the destination's verbatim body), or json (a { statusCode, headers, data } envelope with the destination's status and headers).

  • executeJS — set true to render JavaScript for SPAs when the content comes back empty. Cannot be combined with headers.

  • method + body — use POST/PUT/PATCH with a body to send writes (body is rejected on GET).

  • headers — forward custom request headers. Not supported when executeJS is enabled.

  • countryCode — ISO 3166-1 alpha-2 (e.g. "US") to route through a proxy in that country.

  • solveCaptcha — defaults true; set false to fail fast instead of spending effort solving a challenge.

Returns: Markdown by default; the verbatim body or a JSON envelope when format is set accordingly.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe full URL of the webpage to fetch. Must be a valid HTTP/HTTPS URL.
bodyNoRequest body for POST/PUT/PATCH. A string is sent as-is; an object is JSON-stringified. Not allowed for GET.
formatNoOutput format: 'markdown' for clean LLM-optimized text (recommended), 'raw' for the destination's verbatim body, 'json' for a { statusCode, headers, data } envelope.markdown
methodNoHTTP method for the request. Use POST/PUT/PATCH to send a body.GET
headersNoCustom request headers to forward (max 50). Not supported when executeJS is enabled.
executeJSNoEnable JavaScript rendering for SPAs and dynamic content. Set to true if content appears empty or incomplete. Cannot be combined with custom headers.
countryCodeNoISO 3166-1 alpha-2 country code for geolocated proxy routing, e.g. 'US'.
solveCaptchaNoWhether to attempt captcha solving. Defaults to true server-side; set false to fail fast on challenges.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.8
    • changedInput schema / properties / format / description
      Previous value: -"Output format: 'markdown' for clean LLM-optimized text (recommended), 'raw' for the verbatim upstream body, 'json' for a { statusCode, headers, data } envelope."New value: +"Output format: 'markdown' for clean LLM-optimized text (recommended), 'raw' for the destination's verbatim body, 'json' for a { statusCode, headers, data } envelope."
  2. First observedv1.2.0

TDQS

A4.3/5.0
Behavior3/5

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

It discloses behavior beyond the annotations: captcha solving is attempted by default unless solveCaptcha is false, requests can be routed through country proxies, JS rendering is the remedy for empty SPA content, and headers are incompatible with executeJS. However, the advertised POST/PUT/PATCH 'send writes' path is never reconciled with the readOnlyHint=true annotation, and operational limits (timeouts, response size caps/truncation, rate limiting, error behavior) are unmentioned.

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?

Front-loaded with purpose, then the common case, then best-for/not-for, then optional parameters in diminishing priority; the bolded section headers make it skimmable. Slight redundancy remains in the closing 'Returns' sentence, which largely restates the `format` parameter description, and the inline JSON example adds little for a single required string.

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 an 8-parameter, open-world fetch tool with no output schema, the description covers the return shape (markdown / verbatim body / { statusCode, headers, data } envelope) and the parameter interactions an agent would otherwise get wrong. What is missing are the operational expectations that matter for a scraping tool: timeouts, payload size limits or truncation of very large pages, and failure modes.

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, and the description earns above that by explaining the selection intent behind parameters rather than restating types: the minimal `url`-only call, `format` values with the reason to prefer markdown, `solveCaptcha=false` framed as 'fail fast', and the incompatibility rules between `executeJS`, `headers`, `method`, and `body`. Most of those overlap with the schema text, which keeps it from a 5.

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?

States a specific verb and resource ('Fetch a caller-specified HTTP(S) URL') plus the transformation applied ('clean, LLM-ready Markdown back'). It also explicitly separates itself from the sibling web_access_search, so an agent can pick between the two without opening either 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 an explicit default recommendation ('If available, default to this tool'), a 'Primary use (the common case)' with a minimal one-parameter example, a 'Best for' list, and a 'Not for' clause that names the exact alternative (web_access_search). The optional parameters are additionally framed as 'omit unless you need them', which is real routing guidance.

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