Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Retrieve webpage HTML by URL

web_html_generate
Read-onlyIdempotent

Retrieve cleaned HTML from a webpage URL, with optional CSS wait and full-page scrolling to capture dynamic content before extraction.

Instructions

Retrieve cleaned HTML from an existing webpage at the supplied URL. Requires url.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "web_html_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Web page URL to fetch.
proxyNoMost expensive proxy tier to use. The page is tried on `datacenter` first and moves up only if it is blocked, stopping at this tier. Default: every tier (`mobile`).
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
waitForNoWait for a CSS selector before extraction. Must be prefixed with "css:" (e.g. css:main). JavaScript wait conditions are not supported.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
maxCreditsNoMost credits this call may cost (1–25). Default 1, which loads about 1.6 MB on the datacenter proxy or 190 KB on residential or mobile. Raise it for heavy pages; you're charged only for what the page uses.
scanFullPageNoWhen true, scroll the page to load dynamically appended content (infinite scroll). Default false.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the returned HTML is 'cleaned' and only existing pages are supported — but says nothing about credit consumption, proxy escalation, or the conversation_id sequencing rule that materially affects how the call must be made.

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?

Two short sentences, zero filler, with the core action front-loaded before the parameter note. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with credit caps, proxy tiers and a conversation_id handshake, the description is thin — it conveys what is fetched but not the cost or sequencing behavior an agent should plan around. It leans entirely on the unusually rich schema to cover the gap.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains url, proxy, context, llm_model, maxCredits, waitFor, scanFullPage and conversation_id in detail. The description only echoes the required `url`, adding no meaning beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Retrieve cleaned HTML from an existing webpage at the supplied URL.' The word 'cleaned' implies a post-processed variant, which implicitly separates it from a raw-fetch or markdown sibling, but no sibling is named, so differentiation is left to inference.

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

Usage Guidelines2/5

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

The only guidance is 'Requires `url`', which restates the schema. Nothing tells the agent when to pick this over web_markdown_generate, web_extract_run, or web_crawl_run, nor are there prerequisites or exclusions.

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