Skip to main content
Glama
Artirain

nodemaven-mcp

by Artirain

nodemaven_fetch

Read-only

Bypass geo-restrictions and datacenter blocks by fetching web pages through NodeMaven residential or mobile IPs, returning readable text or JSON.

Instructions

Fetch a URL through a NodeMaven residential or mobile IP and return its content.

Use this when a page is geo-restricted or blocks datacenter traffic. HTML is converted to readable text by default so it does not flood the context; set as_text=false when the markup itself matters.

Returns: str: Markdown or JSON with the schema: { "url": str, # final URL after redirects "status_code": int, "content_type": str, "title": str | None, # HTML when available "latency_ms": int, "truncated": bool, "bytes": int, "body": str, "proxy": str # password-masked proxy URL } On failure: "Error: "

Examples: - "read this page as a German visitor" -> url=..., country='de' - "check the price shown to US shoppers" -> url=..., country='us', city='new york' - Don't use when: the site is reachable without a proxy (use a plain fetch)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ispNoISP or mobile carrier to pin, e.g. 't-mobile usa'.
urlYesAbsolute http(s) URL to fetch through the proxy.
cityNoCity to narrow the pool, e.g. 'los angeles'.
portNoOverride the proxy port. Defaults to the port set for the protocol.
regionNoState or region to narrow the pool, e.g. 'california'.
as_textNoStrip HTML markup and return readable text instead of raw HTML.
countryYesTwo-letter ISO country code for the exit IP, e.g. 'us', 'de', 'br'.
protocolNoProxy protocol: 'http' or 'socks5'.http
ipv4_onlyNoRestrict the exit IP to IPv4.
max_bytesNoTruncate the response body to this many bytes.
session_idNo4-10 alphanumeric characters. Reuse the same value to keep the same exit IP across calls (sticky session); omit it to rotate on every request.
response_formatNo'markdown' for a compact summary, 'json' for the full payload.markdown
ip_quality_filterNoNodeMaven IP quality tier, e.g. 'medium' or 'high'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already establish the tool as readOnly and non-destructive, but the description adds substantial behavioral context beyond that: HTML is converted to readable text by default, responses can be truncated, error messages include remediation details, and the full return schema is provided with fields like truncated and proxy. This gives the agent a clear picture of what to expect.

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 description is well-structured with distinct sections for purpose, usage, return schema, examples, and an explicit anti-caveat. It is somewhat lengthy due to the included return schema, but every section earns its place and the front-loaded purpose/usage makes it efficient to scan.

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?

Given the tool's complexity (13 parameters, rich output), the description is complete: it covers purpose, when to use, return format, error behavior, and examples. The schema provides full parameter documentation, and the description's output schema and 'Don't use' guidance seal any gaps.

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?

Input schema covers 100% of parameters, so baseline is 3. The description adds meaningful usage examples for country and city (e.g., country='de' for German visitor), and clarifies the as_text parameter's behavior. However, it does not discuss all parameters, so the schema remains the primary source for many.

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 description clearly states the tool fetches a URL through a NodeMaven proxy and returns content. It distinguishes this from sibling tools like nodemaven_build_proxy_url and nodemaven_check_proxy by focusing on the actual fetch operation. Examples reinforce the purpose.

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?

Provides explicit 'Use this when' (geo-restricted or blocks datacenter traffic) and 'Don't use when' (site reachable without a proxy) guidance. Also gives contextual examples such as 'read this page as a German visitor' and 'check the price shown to US shoppers' to illustrate parameter usage. Indicates when to set as_text=false for markup.

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/Artirain/nodemaven-mcp'

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