WebLens

search_web

Real-time web search powered by Google. Returns ranked results with titles, URLs, and snippets. Set includeContent to also fetch the top result pages as markdown in the same call. Price: $0.005, plus $0.0015 per result page fetched with includeContent

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": {
      "query": "<query>"
    },
    "name": "search_web"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results to return
`query`	Yes	Search query
`contentChars`	No	Per-page content character cap
`contentResults`	No	How many top results to fetch content for (when includeContent)
`includeContent`	No	Also fetch the top result pages as markdown (+$0.0015 per fetched result)

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 13, 2026
- addedInput schema / properties / contentChars / default
```
Added value: +8000
```
- changedInput schema / properties / contentChars / description
```
Previous value: -"Per-page content character cap (default 8000)"New value: +"Per-page content character cap"
```
- addedInput schema / properties / contentResults / default
```
Added value: +5
```
- changedInput schema / properties / contentResults / description
```
Previous value: -"How many top results to fetch content for (1-10, default: 5)"New value: +"How many top results to fetch content for (when includeContent)"
```
- addedInput schema / properties / contentResults / maximum
```
Added value: +10
```
- addedInput schema / properties / contentResults / minimum
```
Added value: +1
```
- addedInput schema / properties / includeContent / default
```
Added value: +false
```
- changedInput schema / properties / includeContent / description
```
Previous value: -"Also fetch top result pages as markdown (+$0.0015/result)"New value: +"Also fetch the top result pages as markdown (+$0.0015 per fetched result)"
```
- addedInput schema / properties / limit / default
```
Added value: +10
```
- changedInput schema / properties / limit / description
```
Previous value: -"Number of results (default: 10)"New value: +"Maximum results to return"
```
- addedInput schema / properties / limit / example
```
Added value: +10
```
- addedInput schema / properties / limit / maximum
```
Added value: +20
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / query / example
```
Added value: +"x402 payment protocol"
```
- addedInput schema / properties / query / maxLength
```
Added value: +500
```
- addedInput schema / properties / query / minLength
```
Added value: +1
```
First observedAug 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful operational facts: what the response contains, that includeContent triggers additional page fetching within the same call, and an explicit cost model ($0.005 base, $0.0015 per fetched page). It omits auth requirements, rate limits, and failure behavior, which keeps it from a 5.

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?

Three tight sentences with zero filler, front-loading the capability and then the optional behavior and cost. Every sentence adds information an agent would not get from the schema alone.

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?

There is no output schema, but the description compensates by naming the response fields (titles, URLs, snippets) and the markdown content shape. For a five-parameter read tool this is nearly complete; only auth, rate-limit, and error context are absent.

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 description coverage is 100%, so all five parameters are already documented with types, defaults, and bounds, making 3 the baseline. The description adds only marginal value by restating the includeContent cost implication and nothing about query syntax or how limit interacts with contentResults.

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?

States a specific verb and resource ('Real-time web search powered by Google') and describes the return payload (titles, URLs, snippets), which lets an agent distinguish it from fetch_webpage and get_contents. It stops short of explicitly differentiating itself from sibling search variants like search_news or search_scholar, so the agent must infer the general-purpose intent.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance, and no sibling alternatives are named. The one usage cue is implicit: 'Set includeContent to also fetch the top result pages as markdown in the same call,' which hints this can replace a separate fetch step, but the agent must work out when general web search beats the specialized search siblings.

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

All WebLens tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.