Skip to main content
Glama

web

Search the web via DuckDuckGo, crawl pages for content, and fetch news articles. Save results to disk using harvest to avoid high context costs.

Instructions

Web search and page fetching. Returns {success, results/content, url}. Use ONLY after exhausting local sources: retrieve() -> kg(neighbors) -> web. Actions: 'search' (DuckDuckGo, returns title/url/snippet), 'crawl' (fetch page content). Set news=true for DDG news endpoint (adds date/source fields). High context cost - prefer harvest=True to save content to disk instead of loading into context. Results cached 20min. For bot-protected sites, use fx tool instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to crawl. Required for action='crawl'.
newsNoUse DDG news endpoint instead of web. Returns date/source per result. search action only.
queryNoSearch query. Required for action='search'.
actionYes'search' for DuckDuckGo query, 'crawl' to fetch a specific URL
harvestNoSave content to disk, return metadata only. Saves context tokens.
summaryNoReturn summary only (default: true). Set false for full page content.
timelimitNoTime filter for news: 'd' (day), 'w' (week), 'm' (month).
harvest_destNoSubfolder under harvested/ (e.g., 'docs/'). Required if harvest=true.
timeout_secondsNoRequest timeout. Default: 30.
Behavior5/5

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

With no annotations, the description fully discloses: caching (20 min), high context cost, harvest behavior, default summary, news endpoint fields, timeout default. No contradictions.

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

Conciseness5/5

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

Compact paragraph with front-loaded purpose and clear logical flow: purpose, usage order, action details, news, cost mitigation, caching, alternatives. Every sentence adds value.

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

Completeness5/5

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

Given 9 parameters and no output schema, the description covers all essential aspects: what it does, how to use, parameter details, behavior, caching, context management, and alternative tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds meaning: groups actions, explains harvest as context-saving, news adds date/source, timelimit for news, harvest_dest subfolder, summary default true.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Web search and page fetching' and specifies two actions (search via DuckDuckGo, crawl via URL fetch). Explicitly distinguishes from sibling tool fx for bot-protected sites.

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

Usage Guidelines5/5

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

Provides explicit usage order: 'Use ONLY after exhausting local sources: retrieve() -> kg(neighbors) -> web.' Also advises using fx for bot-protected sites and suggests harvest=True to save context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cutlerbenjamin1-cmd/web-explorer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server