Skip to main content
Glama

Web search API with contents: Exa-style search, filters, page text and highlights

search
Read-only

Exa-style web search: top 1-20 results with title, URL, snippet, published date and favicon (Brave index); optional domain, date, category and phrase filters; optional live page text, highlights and AI summaries of the top 10 pages. Results are for immediate use only: no storing, resale or model training (Brave API terms). Failures return 503, uncharged. Use when an agent needs current information or sources from the open web. Example: q=x402 payment protocol. Price $0.01/call via x402 USDC or a card key (/credits); failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query, at most 400 characters
countNoNumber of results (1-20, default 10)
countryNoLocalize results for this country: 2-letter code (SE, DE, FR, GB, US…)
summaryNotrue: a 1-3 sentence AI summary of each of the top pages
categoryNonews, research paper, github, pdf, tweet, linkedin profile, company, personal site or financial report
textCharsNoReturn the live page text of the top results, this many characters each (500-20000, or true for 3000; default none)
highlightsNotrue: the passages of each page that best match the query, with scores
excludeTextNoA phrase the results must not contain
includeTextNoA phrase the results must contain (up to 5 words)
numSentencesNoSentences per highlight (1-10, default 3)
summaryQueryNoWhat the summaries should focus on (default: the query)
excludeDomainsNoNever results from these domains: comma list or JSON array
includeDomainsNoOnly results from these domains: comma list or JSON array, up to 20 (example.com, github.com/org)
endPublishedDateNoOnly pages published on or before this date (ISO 8601)
highlightsPerUrlNoHighlights per result (1-5, default 1)
startPublishedDateNoOnly pages published on or after this date (ISO 8601, e.g. 2025-01-01)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / count / maximum
      Previous value: -9007199254740991New value: +20
    • changedInput schema / properties / count / minimum
      Previous value: --9007199254740991New value: +1
    • changedInput schema / properties / highlightsPerUrl / maximum
      Previous value: -9007199254740991New value: +5
    • changedInput schema / properties / highlightsPerUrl / minimum
      Previous value: --9007199254740991New value: +1
    • changedInput schema / properties / numSentences / maximum
      Previous value: -9007199254740991New value: +10
    • changedInput schema / properties / numSentences / minimum
      Previous value: --9007199254740991New value: +1
    • changedInput schema / properties / textChars / maximum
      Previous value: -9007199254740991New value: +20000
    • changedInput schema / properties / textChars / minimum
      Previous value: --9007199254740991New value: +500
  2. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Localize results for this country: 2-letter code (SE, DE, FR, GB, US…)",
      +  "type": "string"
      +}
  3. Changed13 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "news, research paper, github, pdf, tweet, linkedin profile, company, personal site or financial report",
      +  "type": "string"
      +}
    • addedInput schema / properties / endPublishedDate
      Added value: +{
      +  "description": "Only pages published on or before this date (ISO 8601)",
      +  "type": "string"
      +}
    • addedInput schema / properties / excludeDomains
      Added value: +{
      +  "description": "Never results from these domains: comma list or JSON array",
      +  "type": "string"
      +}
    • addedInput schema / properties / excludeText
      Added value: +{
      +  "description": "A phrase the results must not contain",
      +  "type": "string"
      +}
    • addedInput schema / properties / highlights
      Added value: +{
      +  "description": "true: the passages of each page that best match the query, with scores",
      +  "type": [
      +    "string",
      +    "number",
      +    "boolean"
      +  ]
      +}
    • addedInput schema / properties / highlightsPerUrl
      Added value: +{
      +  "description": "Highlights per result (1-5, default 1)",
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / includeDomains
      Added value: +{
      +  "description": "Only results from these domains: comma list or JSON array, up to 20 (example.com, github.com/org)",
      +  "type": "string"
      +}
    • addedInput schema / properties / includeText
      Added value: +{
      +  "description": "A phrase the results must contain (up to 5 words)",
      +  "type": "string"
      +}
    • addedInput schema / properties / numSentences
      Added value: +{
      +  "description": "Sentences per highlight (1-10, default 3)",
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / startPublishedDate
      Added value: +{
      +  "description": "Only pages published on or after this date (ISO 8601, e.g. 2025-01-01)",
      +  "type": "string"
      +}
    • addedInput schema / properties / summary
      Added value: +{
      +  "description": "true: a 1-3 sentence AI summary of each of the top pages",
      +  "type": [
      +    "string",
      +    "number",
      +    "boolean"
      +  ]
      +}
    • addedInput schema / properties / summaryQuery
      Added value: +{
      +  "description": "What the summaries should focus on (default: the query)",
      +  "type": "string"
      +}
    • addedInput schema / properties / textChars
      Added value: +{
      +  "description": "Return the live page text of the top results, this many characters each (500-20000, or true for 3000; default none)",
      +  "maximum": 9007199254740991,
      +  "minimum": -9007199254740991,
      +  "type": "integer"
      +}
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/idempotent/destructive, yet the description adds genuinely new behavioral facts: results are for immediate use only (no storing, resale, or model training per Brave terms), failures return 503 and are uncharged, and each call costs $0.01 via x402 USDC or a card key. The closing 'Reads or computes only and changes nothing; each call is charged, so repeats are not free' partly restates the annotations but usefully ties cost to the idempotentHint=false.

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

Conciseness4/5

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

Front-loaded with the core capability and result shape, then filters, enrichments, licensing, error behavior, and pricing in a compact semicolon-delimited block. A few clauses duplicate structured data (the read-only restatement, the free-failure note appearing twice), but the density is mostly justified for a 16-parameter tool.

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 broad open-world search with no output schema, the description sketches return fields, defines failure behavior (503, uncharged), and discloses licensing and payment requirements. Remaining gaps — pagination/result-set truncation, rate limits, and how the /credits key is supplied — are modest but real.

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?

Schema coverage is 100%, so each of the 16 parameters is already documented individually and the baseline is 3. The description adds only light grouping semantics — that domain/date/category/phrase filters exist and that text, highlights, and summaries apply to the top 10 pages — without explaining formats or interactions beyond what the schema states.

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

Purpose4/5

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

Opens with a specific verb and resource — 'Exa-style web search' returning 'top 1-20 results with title, URL, snippet, published date and favicon' — and enumerates the enrichments (page text, highlights, AI summaries). The 'open web' framing implicitly separates it from the specialized siblings (arxiv_search, github_search, company_search), though no sibling is named outright.

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?

'Use when an agent needs current information or sources from the open web' gives clear selection context, reinforced by a concrete example query (q=x402 payment protocol). There are no explicit when-not conditions or named alternatives, so the agent must infer that targeted-index siblings are preferable for niche sources.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.