Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Crawl web pages

web_crawl_run
Read-onlyIdempotent

Crawl up to five supplied URLs synchronously and return extracted page content as a list for web research and data collection.

Instructions

Crawl a small set of web pages synchronously. Requires url. Returns a list.

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_crawl_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. URLs to crawl. Repeat the `url` query parameter for multiple pages (max 5).
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 each URL may cost (1–25). Default 1. The batch shares one budget of this times the number of URLs; you're charged for what the pages use, at least 1 credit per URL.
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.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world behavior, so the description only needs to add context. It contributes that execution is synchronous and that the result is a list, but omits any mention of credit budgeting, proxy tiers, or the conversation_id sequencing constraint that the schema treats as mandatory behavior.

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?

Three short sentences with the key fact (synchronous, small batch) front-loaded and no filler. The closing 'Returns a list' is padded and vague, though it costs little space.

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

Completeness2/5

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

This is a fairly complex tool: eight parameters, three required, a shared credit budget, tiered proxies, and a conversation_id handshake, with no output schema. The description addresses none of these and describes the return value only as 'a list', which is not enough for an agent to call it confidently without reading every schema field.

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% and all eight parameters carry their own detailed descriptions, including ranges and defaults. The description only restates that `url` is required and says nothing about the other required fields (`context`, `llm_model`) or cost/ordering parameters, so it adds no meaning beyond the schema.

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?

The description names a specific verb ('Crawl') and resource ('web pages') and scopes it ('a small set', 'synchronously'), so an agent can distinguish it from a single-page fetch. It does not name or contrast with sibling tools like web_extract_run or web_search_run, which keeps it 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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. 'Small set' and 'synchronously' only weakly imply that large batches or async workflows need a different tool, leaving the agent to infer routing.

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