Skip to main content
Glama

search

Search the web to retrieve full page content for factual lookups and specific questions. Optionally get AI-synthesized answers or filter by news and recency.

Instructions

Search the web for current information on any topic. Returns extracted page content, not just snippets. Best for factual lookups, specific questions, or when you need a list of sources. For open-ended questions that need synthesis across many sources, use the research tool instead.

For news queries (current events, breaking news, politics, world events), set topic="news" to search news sources specifically. This returns recent articles with publication dates.

Set include_answer=true to get an AI-synthesized answer alongside results (adds 5 credits). This is the sweet spot for most agent tasks, e.g. basic + include_answer = 8 credits, much cheaper than a full 25-credit research call.

Returns: query, answer (if requested), results (array of {title, url, content, description, fetched, published_date}), search_depth, topic, elapsed_ms, credits_used, credits_remaining, altered_query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query
topicNo"general" for web search, "news" for news articles. Use "news" for current events, breaking news, politics, or any time-sensitive querygeneral
freshnessNoFilter by recency: "day", "week", "month", "year", or "YYYY-MM-DD:YYYY-MM-DD"
max_resultsNoNumber of results (default 10, max 20)
search_depthNo"basic" (default) for extracted page content (3 credits), "snippets" for SERP snippets only without page fetching (1 credit)basic
include_answerNoGenerate an AI answer that synthesizes the search results (adds 5 credits)
exclude_domainsNoExclude results from these domains (max 10)
include_domainsNoOnly include results from these domains (max 10)
Behavior5/5

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

With no annotations, the description fully compensates by disclosing credit costs for different search depths and include_answer, comparing costs to research (8 vs 25 credits), and detailing the return structure including 'altered_query'.

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?

The description is well-structured with clear paragraphs: purpose, news guidance, cost details, and return fields. Every sentence is informative, front-loaded with purpose, and no superfluous text.

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?

Despite having 8 parameters and no output schema, the description covers purpose, usage guidelines, parameter behavior, costs, and return format comprehensively. It addresses the tool's complexity adequately.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for all parameters. The description adds value by explaining credit costs and recommending when to use topic='news' and include_answer, going beyond schema alone.

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?

The description clearly states the tool's function: 'Search the web for current information on any topic' and notes it returns extracted page content. It distinguishes from the research sibling by directing open-ended synthesis questions there.

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?

Explicitly states when to use: 'Best for factual lookups, specific questions, or when you need a list of sources' and when not: 'For open-ended questions that need synthesis across many sources, use the research tool instead.' Also provides guidance for news queries with topic='news'.

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/sofya-co/sofya-mcp'

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