Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Ask a question about a web page

web_ask_run
Read-onlyIdempotent

Ask a natural-language question about a specific web page and receive an LLM-generated answer, so you can extract needed facts without reading the full page.

Instructions

Ask a natural-language question about a specific web page and get an LLM-generated answer. Requires url and q. Put the question in q, e.g. {"url":"https://example.com","q":"What does this company sell?"}.

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

Input Schema

NameRequiredDescriptionDefault
qYesRequired. Natural-language question to answer about the page content.
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.
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). One credit covers loading a typical page and the model reading roughly 1,500 words of it (less in languages such as Japanese); long pages are answered from their first part (`truncated: true`) unless you raise this. Charged only for what the call 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so safety is covered. The description adds that the answer is LLM-generated and that a URL must be fetched, which is real context beyond the annotations. It says nothing about credit cost, page truncation, or the conversation_id handshake, all of which live 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.

Conciseness4/5

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

Three short sentences, front-loaded with purpose, and the worked example clarifies argument roles at a glance. The example is somewhat redundant with a fully documented schema, keeping it from a 5.

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

Completeness4/5

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

For a single-question page Q&A tool, the description tells an agent everything needed to form a correct call, and the rich schema covers credits, proxy tiers and the conversation_id echo. No output schema exists, but the description's claim of an LLM-generated answer adequately sets expectations for the return.

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 baseline is 3. The description repeats that `url` and `q` are required and gives an example payload, but adds no meaning beyond what the schema already documents for those fields.

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 states a specific verb and resource: ask a natural-language question about a specific web page and receive an LLM-generated answer. That cleanly separates it from extraction (web_extract_run) or crawl siblings in spirit, though no sibling is named. It is clear but stops short of explicit differentiation.

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

Usage Guidelines3/5

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

Usage is only implied: you need a specific page URL and a question about that page's content. There is no statement of when to prefer this over a search tool, a crawl, or a plain extract call, and no 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