Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EXA_API_KEYNoAPI key for Exa search service. Enables Exa source when configured.
SEARXNG_URLNoURL of the SearXNG server. Enables SearXNG source when configured.
SERPER_API_KEYNoAPI key for Serper search service. Enables Serper source when configured.
TAVILY_API_KEYNoAPI key for Tavily search service. Enables Tavily source when configured.
X_BEARER_TOKENNoBearer token for X / Twitter recent search API. Enables X source when configured.
SERPAPI_API_KEYNoAPI key for SerpAPI search service. Enables SerpAPI source when configured.
YOUTUBE_API_KEYNoAPI key for YouTube Data API. Enables YouTube source when configured.
DOUYIN_DEVICE_IDNoDouyin device identifier (Int64). Required for Douyin source.
REDDIT_CLIENT_IDNoReddit OAuth client ID. Required for Reddit source.
DOUYIN_CLIENT_KEYNoDouyin client key. Required for Douyin source (along with DOUYIN_CLIENT_SECRET and DOUYIN_DEVICE_ID).
REDDIT_USER_AGENTNoOptional Reddit user agent.
DEEP_WEBSEARCH_HOMENoBase directory for configuration and shared runtime. Used to locate config.yaml and .env when not specified otherwise.
BRAVE_SEARCH_API_KEYNoAPI key for Brave Web Search API. Enables Brave source when configured.
DOUYIN_CLIENT_SECRETNoDouyin client secret. Required for Douyin source.
REDDIT_CLIENT_SECRETNoReddit OAuth client secret. Required for Reddit source.
REDDIT_REFRESH_TOKENNoOptional Reddit OAuth refresh token.
DEEP_WEBSEARCH_CONFIGNoAbsolute path to the config.yaml file.
DEEP_WEBSEARCH_ENV_FILENoAbsolute path to the .env file.
DEEP_WEBSEARCH_HEADLESSNoSet to 'true' to disable desktop notifications (headless mode).

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
source_statusA

List every source's configuration readiness; probe=True performs network initialization checks.

broad_searchA

Search all configured sources across bounded query expansion rounds with citations and coverage.

sources=None selects all available sources; explicit sources limits native searches. Missing sources are skipped and reported. Optional web_index_fallback uses enabled web engines to supplement unavailable requested platforms using site: filters; it never counts as successful native platform search. queries adds concrete seed queries, including alternate-language queries designed by the caller.

fetch_pageA

Extract bounded original HTML/text evidence from a public URL; redirects and DNS are validated.

fetch_pagesB

Read up to 10 public evidence pages; individual failures do not discard successful extractions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation4/5

Each tool targets a distinct operation: source_status is diagnostics, broad_search is search, and fetch_page/fetch_pages are single vs. batched retrieval. The fetch_page vs. fetch_pages pair could be momentarily confused, but descriptions clearly distinguish single-URL extraction from batch reading up to 10 pages.

Naming Consistency4/5

All names use consistent snake_case (source_status, broad_search, fetch_page, fetch_pages), and the fetch_ prefix cleanly pairs the single/batch variants. source_status is noun_noun rather than the verb_noun pattern of the others, a minor deviation.

Tool Count4/5

Four tools is a lean but sensible scope for a search-and-fetch server: one diagnostic, one search, and two retrieval tools. It is slightly thin (no dedicated source-listing or pagination tool), but each tool clearly earns its place.

Completeness4/5

The surface covers the core lifecycle: check source readiness, run broad search with citations, and extract evidence from single or multiple pages. Minor gaps exist (e.g., explicit source enumeration or result pagination), but agents can work around these via source_status and broad_search parameters.

Maintenance

ActivityMaintained
ResponsivenessNo issues