Skip to main content
Glama
fusionproxy-mcp

fusionproxy-mcp

Official

fetch_page

Fetch public web pages through residential IPs in a chosen country, preserve session IPs, and return content as Markdown, plain text, or HTML.

Instructions

Fetch a public web page through a residential IP and return its content.

Args: url: http(s) URL of the page. country: two-letter country code of the exit IP (for example "us", "de", "jp"). Optional. session: any name; calls with the same name keep the same IP for 10 minutes. Optional. output: "markdown" (default, readable), "text" or "html" (raw). max_chars: cut the result to this many characters (default 20000).

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

Input Schema

NameRequiredDescriptionDefault
urlYes
outputNomarkdown
countryNo
sessionNo
max_charsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: traffic egresses via a residential IP, sessions pin the same IP for 10 minutes, and results are truncated by max_chars. It omits failure modes, timeouts, JS rendering, and cost/rate limits, which keeps it from a 5.

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?

The one-line summary is front-loaded and states the essentials before the Args breakdown. The Args block is somewhat list-like but earns its place given zero schema coverage; no sentence is redundant.

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 a five-parameter read tool with an output schema (so return values need no explanation), the description covers mechanism, geo-selection, session behavior, and truncation. The remaining gap is operational behavior on failures or rate limits.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate entirely, and it does: every one of the five parameters is explained with semantics beyond the schema, including the meaning of the output enum values ('markdown' readable, 'html' raw), the 10-minute session stickiness, and truncation via max_chars.

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 web page) plus the distinguishing mechanism (residential IP) and the result (page content). This clearly separates it from a sibling like check_exit_ip, which only inspects the exit IP rather than retrieving page content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'public web page' hints that non-public or authenticated pages are out of scope, but the description never states when to use this tool versus alternatives, nor any exclusions. An agent gets context but no explicit routing guidance.

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

Deploy Server

Other Tools