Skip to main content
Glama
w-jeon

mcp-brave-search

by w-jeon

brave_web_search

Perform web searches using the Brave Search API to gather diverse online content, news, or articles. Supports pagination, content filtering, and freshness controls for precise results.

Instructions

Performs a web search using the Brave Search API, ideal for general queries, news, articles, and online content. Use this for broad information gathering, recent events, or when you need diverse web sources. Supports pagination, content filtering, and freshness controls. Maximum 20 results per request, with offset for pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results (1-20, default 10)
offsetNoPagination offset (max 9, default 0)
queryYesSearch query (max 400 chars, 50 words)

Implementation Reference

  • Core implementation of the brave_web_search tool: makes API call to Brave Search, handles response, extracts and formats web search results.
    async function performWebSearch(query: string, count: number = 10, offset: number = 0) {
      checkRateLimit();
      const url = new URL('https://api.search.brave.com/res/v1/web/search');
      url.searchParams.set('q', query);
      url.searchParams.set('count', Math.min(count, 20).toString()); // API limit
      url.searchParams.set('offset', offset.toString());
    
      const response = await fetch(url, {
        headers: {
          'Accept': 'application/json',
          'Accept-Encoding': 'gzip',
          'X-Subscription-Token': BRAVE_API_KEY
        }
      });
    
      if (!response.ok) {
        throw new Error(`Brave API error: ${response.status} ${response.statusText}\n${await response.text()}`);
      }
    
      const data = await response.json() as BraveWeb;
    
      // Extract just web results
      const results = (data.web?.results || []).map(result => ({
        title: result.title || '',
        description: result.description || '',
        url: result.url || ''
      }));
    
      return results.map(r =>
        `Title: ${r.title}\nDescription: ${r.description}\nURL: ${r.url}`
      ).join('\n\n');
    }
  • Tool schema definition for brave_web_search including name, description, and input schema.
    const WEB_SEARCH_TOOL: Tool = {
      name: "brave_web_search",
      description:
        "Performs a web search using the Brave Search API, ideal for general queries, news, articles, and online content. " +
        "Use this for broad information gathering, recent events, or when you need diverse web sources. " +
        "Supports pagination, content filtering, and freshness controls. " +
        "Maximum 20 results per request, with offset for pagination. ",
      inputSchema: {
        type: "object",
        properties: {
          query: {
            type: "string",
            description: "Search query (max 400 chars, 50 words)"
          },
          count: {
            type: "number",
            description: "Number of results (1-20, default 10)",
            default: 10
          },
          offset: {
            type: "number",
            description: "Pagination offset (max 9, default 0)",
            default: 0
          },
        },
        required: ["query"],
      },
    };
  • index.ts:311-313 (registration)
    Registers the brave_web_search tool by including WEB_SEARCH_TOOL in the tools list for ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [WEB_SEARCH_TOOL, LOCAL_SEARCH_TOOL],
    }));
  • Dispatch handler in CallToolRequestSchema that validates arguments and invokes performWebSearch for brave_web_search.
    case "brave_web_search": {
      if (!isBraveWebSearchArgs(args)) {
        throw new Error("Invalid arguments for brave_web_search");
      }
      const { query, count = 10 } = args;
      const results = await performWebSearch(query, count);
      return {
        content: [{ type: "text", text: results }],
        isError: false,
      };
    }
  • Type guard for validating input arguments to brave_web_search tool.
    function isBraveWebSearchArgs(args: unknown): args is { query: string; count?: number } {
      return (
        typeof args === "object" &&
        args !== null &&
        "query" in args &&
        typeof (args as { query: string }).query === "string"
      );
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and does this well. It reveals important behavioral traits including maximum results per request (20), pagination support with offset, content filtering capabilities, freshness controls, and the general nature of the search. It doesn't mention rate limits or authentication requirements, but provides substantial operational context.

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 perfectly structured and concise - three sentences that each earn their place. The first establishes purpose and ideal use cases, the second provides operational context, and the third specifies limitations. No wasted words, front-loaded with the most important information.

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

Completeness4/5

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

For a search tool with no annotations and no output schema, the description provides substantial context about behavior, limitations, and use cases. It covers the essential operational aspects (pagination, filtering, freshness controls, result limits) but doesn't describe the return format or structure of results, which would be helpful given the lack of output schema.

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?

With 100% schema description coverage, the schema already documents all three parameters thoroughly. The description adds some context about pagination ('Supports pagination... with offset for pagination') and result limits ('Maximum 20 results per request'), but doesn't provide additional semantic meaning beyond what's in the schema descriptions. This meets the baseline for high schema coverage.

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 purpose with specific verbs ('performs a web search') and resources ('using the Brave Search API'), distinguishing it from the sibling tool 'brave_local_search' by specifying it's for general web content rather than local searches. It explicitly mentions the types of content it's ideal for (general queries, news, articles, online content).

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('for broad information gathering, recent events, or when you need diverse web sources'), but doesn't explicitly state when NOT to use it or provide specific alternatives beyond the implied sibling tool distinction. It offers good guidance but lacks explicit exclusions or named alternatives.

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

Related 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/w-jeon/mcp-brave-search'

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