Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Generate web page markdown

web_markdown_generate
Read-onlyIdempotent

Convert a web page URL into clean Markdown for reading or downstream processing, with optional filters to remove boilerplate or rank relevant content.

Instructions

Convert a web page URL into clean markdown. 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_markdown_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`).
queryNoOptional query string used by the bm25 filter to rank relevant content.
filterNoMarkdown extraction filter. `fit`: strip boilerplate and extract the main readable content. `raw`: full unfiltered page markdown, no content pruning. `bm25`: rank and return only the content most relevant to `query`, using the BM25 keyword-relevance algorithm — requires `query` to be set.fit
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.
cacheModeNoCache behavior. `enabled`: read from cache if present, else fetch and write to cache. `bypass`: always fetch fresh, ignoring and not updating the cache. `write_only`: always fetch fresh, but write the result to cache without reading from it first. Default: `enabled`.enabled
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

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the description is not carrying the safety burden. Beyond that it discloses nothing about the behaviors an agent actually needs to reason about: the tiered proxy escalation, credit budgeting via maxCredits, caching behavior, or the conversation_id handshake that forbids parallel calls before the server issues one. All of that lives only in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the core action is front-loaded. However, the second sentence ('Requires `url`.') repeats what the schema's required list already guarantees and therefore does not earn its place.

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 an 11-parameter tool with three required parameters, enum-driven filter modes, a cost ceiling, and a stateful conversation_id protocol. Against that complexity a two-sentence description is thin, and the absence of an output schema means the description should say something about what the returned markdown looks like (filter-dependent output, truncation under low maxCredits) but does not.

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 parameter meaning is fully documented in structured fields and the baseline of 3 applies. The description adds nothing beyond restating that `url` is required, which is already in the schema's required array and property description.

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 gives a specific verb and resource: convert a web page URL into markdown. An agent can tell this is an extraction/format-conversion tool. It does not differentiate from the closely named sibling web_html_generate, 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?

There is no when-to-use guidance: nothing says when to prefer this over web_html_generate, web_extract_run, or web_ask_run. The only guidance is the prerequisite 'Requires `url`', which is already enforced by the schema's required list.

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