Skip to main content
Glama
usestring

String AI Web Access MCP Server

Official
by usestring
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

web_access_fetch

Fetch any webpage and get clean, LLM-ready Markdown. Handles anti-bot protection, CAPTCHAs, and JavaScript rendering automatically.

Instructions

Fetch any webpage and get clean, LLM-ready Markdown back. String AI's Web Access API handles proxy rotation, anti-bot protection, CAPTCHAs, and JavaScript-rendered content automatically. 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 with anti-bot protection, paywalls, or dynamic content (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 (verbatim upstream 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.

Input Schema

TableJSON 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 verbatim upstream 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.

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses automatic proxy rotation, anti-bot protection, CAPTCHA handling, JavaScript rendering, and restrictions like executeJS not combinable with headers. Lacks mention of rate limits or size limits, but still fairly transparent.

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?

Well-structured with sections, bold text, and a code example. Slightly lengthy but justified by the number of parameters. Every sentence adds value.

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?

Despite 8 parameters and no output schema, the description thoroughly explains each parameter, defaults, return formats, and common use cases. Sufficient for an AI agent to use correctly.

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%, but description adds beyond schema by grouping parameters as optional, explaining primary use (only url needed), and highlighting constraints (e.g., body rejected on GET, executeJS/headers incompatibility).

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?

Clearly states 'Fetch any webpage and get clean, LLM-ready Markdown back.' Distinguishes from sibling tools by specifying it is for URLs, not for searching (use web_access_search instead).

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?

Explicitly recommends defaulting to this tool for web fetching, and advises against using it for search without a URL. Provides a primary use case example and explains when to omit optional parameters.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/usestring/string-ai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server