xpay✦ Marketing Collection

web_search_exa

Search the web for any topic and get clean, ready-to-use content.

  Best for: Finding current information, news, facts, people, companies, or answering questions about any topic.
  Returns: Clean text content from top search results.

  Query tips: 
  describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue".
  Use category:people / category:company to search through Linkedin profiles / companies respectively.
  If highlights are insufficient, follow up with web_fetch_exa on the best URLs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Natural language search query. Should be a semantically rich description of the ideal page, not just keywords. Optionally include category:<type> (company, people) to focus results — e.g. 'category:people John Doe software engineer'.
`numResults`	No	Number of search results to return (must be a number, default: 10).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed7 schema fields changedApr 19, 2026

removedInput schema / properties / contextMaxCharacters

Removed value: -{
-  "description": "Maximum characters for context string optimized for LLMs (must be a number, default: 10000)",
-  "type": "number"
-}

removedInput schema / properties / livecrawl

Removed value: -{
-  "description": "Live crawl mode - 'fallback': use live crawling as backup if cached content unavailable, 'preferred': prioritize live crawling (default: 'fallback')",
-  "enum": [
-    "fallback",
-    "preferred"
-  ],
-  "type": "string"
-}

changedInput schema / properties / numResults / description

Previous value: -"Number of search results to return (must be a number, default: 8)"New value: +"Number of search results to return (must be a number, default: 10)."

addedInput schema / properties / numResults / maximum
```
Added value: +100
```
addedInput schema / properties / numResults / minimum
```
Added value: +1
```

changedInput schema / properties / query / description

Previous value: -"Websearch query"New value: +"Natural language search query. Should be a semantically rich description of the ideal page, not just keywords. Optionally include category:<type> (company, people) to focus results — e.g. 'category:people John Doe software engineer'."

removedInput schema / properties / type

Removed value: -{
-  "description": "Search type - 'auto': balanced search (default), 'fast': quick results",
-  "enum": [
-    "auto",
-    "fast"
-  ],
-  "type": "string"
-}

First observedMar 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses the return type ('Clean text content from top search results') and mentions 'highlights,' indicating what the agent can expect. It also gives query tips that affect search behavior. While not exhaustive (no mention of rate limits or errors), it is reasonably transparent for a search tool.

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 short labeled sections (Best for, Returns, Query tips), front-loads the core purpose, and has no filler. Every sentence contributes actionable information, making it concise and easy to scan.

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?

With 100% schema coverage, no output schema, and only two parameters, the description provides sufficient context for a search tool. It explains what the tool returns and offers usage tips, but could slightly expand on result ordering or error handling to be fully complete.

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?

The input schema covers both parameters with detailed descriptions (100% coverage), but the description adds value beyond the schema by explaining the query style ('describe the ideal page, not keywords') and category usage ('Use category:people / category:company'). This enriches the semantics without redundancy.

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?

The description clearly states the tool performs a web search and returns 'clean, ready-to-use content.' It names the resource (the web) and the action (search), but does not explicitly differentiate from sibling search tools like tavily_search, so it falls short of a 5.

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 a clear 'Best for' list and practical query tips, establishing when to use the tool. It also recommends following up with web_fetch_exa when highlights are insufficient, naming an alternative. However, it does not explicitly state when not to use this tool versus other search tools.

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

All xpay✦ Marketing Collection tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?