Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Capture a web page's network responses

web_network_capture
Read-onlyIdempotent

Load a web page and capture JSON and other network responses its scripts fetch during loading, filtered by a URL match, to inspect API data used by the page.

Instructions

Load a web page and return the JSON and other responses its own scripts fetch while it loads. Requires url and match.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Web page URL to load.
matchYesPart of the request URL to keep, for example `/api/` or `/graphql`. Only fetch and XHR requests whose URL contains it are returned.
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`).
waitMsNoHow long to keep listening after the page loads, in milliseconds (0–15000). Default 4000.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.
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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that only script-initiated fetches are captured, which is useful context, but it omits cost/credit consumption, proxy escalation behavior and timing characteristics that matter for an open-world capture. It also says 'while it loads' while the schema's waitMs implies listening after load, a mild gap but not a contradiction.

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 with no filler, front-loading what is captured and the mechanism. Nothing is padded or restated redundantly beyond the brief required-parameter note.

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?

This is a complex tool with 8 parameters, proxy tiering, credit budgeting and a conversation_id handshake, and no output schema. The description covers what is captured but says nothing about what the return looks like (list of requests/responses?), pacing of conversation_id, or credit consumption, leaving the agent to mine the schema. Adequate but thin for the tool's complexity.

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 every one of the 8 parameters is already documented, including match's substring semantics via the example '/api/'. The description only restates the two main required params and adds no new meaning, so the baseline 3 applies. It also says 'Requires `url` and `match`' while context and llm_model are likewise required in the schema, slightly understating the required set.

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 concrete verb and resource ('Load a web page and return the JSON and other responses its own scripts fetch'), which is meaningfully distinct from screenshotting or markdown extraction. It does not explicitly name a sibling such as web_extract_run to route against, so it stops short of a 5.

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` and `match`,' which is a parameter prerequisite rather than when-to-use guidance. Nothing tells the agent when to choose this over web_extract_run, web_html_generate or web_screenshot_capture, nor are there any 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