Skip to main content
Glama
doranobik

mcp-web-search

by doranobik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
webSearchA

Search the web using DuckDuckGo. Use this tool when you need to find current information, news, documentation, or answers to questions from the internet.

  • No API key required

  • Results include title, URL, and snippet for each result

  • Use the region parameter to get localized results (e.g., 'jp-ja' for Japanese)

  • After getting search results, use fetchWebContent to read full page content from any URL

fetchWebContentA

Fetch and extract the main text content from a webpage. Use this tool after webSearch to read the full content of a specific URL, or when given a direct URL to analyze.

  • Extracts readable article text, removing ads, navigation, and other non-content elements

  • Works best with article pages, blog posts, and documentation

  • May not work well with heavily JavaScript-rendered pages or pages requiring login

  • Use maxChars to limit returned content length for large pages

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

TDQS

A4.5/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: webSearch for querying the web and fetchWebContent for retrieving page content. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tool names follow a consistent camelCase verb-noun pattern (webSearch, fetchWebContent), making them predictable and easy to understand.

Tool Count4/5

With only 2 tools, the server is minimal but well-scoped for its stated purpose of web search and content fetching. While the typical range is 3-15, this lean set is appropriate for the narrow domain.

Completeness5/5

The server covers the essential workflow of searching the web and then fetching full content from selected URLs. No critical operations are missing for its intended use case.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources