Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search the web

web_search_run
Read-onlyIdempotent

Searches the public web and returns ranked organic results with snippets so agents can find relevant pages and sources; supports pagination, region, and date filters.

Instructions

Search the public web and return ranked organic results with snippets. Requires query. Returns a list (use page when paginated).

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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "web_search_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based). Default: 1.
queryYesRequired. Search query text to run against the public web.
regionNoISO 3166-1 country code for localized results (e.g. US, GB, CA).
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.
datePostedNoOptional filter by when results were posted.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds that results are ranked organic results with snippets and that pagination exists, but says nothing about rate limits, result caps, or the conversation_id handshake that the schema flags as sequencing-critical.

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?

Two short sentences, front-loaded with the core action and return shape, with no filler. The parenthetical pagination note is compact and useful rather than 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 a 7-parameter tool with no output schema, the description covers the essentials of what comes back ('a list') but omits the multi-call sequencing constraint around conversation_id and the existence of region/datePosted filtering. It is adequate but leaves the agent to rely entirely on the schema for call-order behavior.

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 parameter including query, page, region, datePosted, and conversation_id is already documented in the schema. The description only restates that query is required and points at page, adding no meaning beyond the structured 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?

States a specific verb and resource ('Search the public web') plus the return shape ('ranked organic results with snippets'). It does not differentiate itself from close siblings like web_ask_run or web_crawl_run, so an agent must infer the boundary.

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 usage hint is 'use page when paginated', which is a pagination note rather than when-to-use guidance. There is no statement of when to prefer this over web_ask_run, web_crawl_run, or web_extract_run, and no 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