WebLens

search_news

Real-time news search via Google News. Returns up to 10 ranked articles with snippet, source, date, and thumbnail. Price: $0.005

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_news"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum results to return
`query`	Yes	Search query

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 13, 2026
- addedInput schema / properties / limit / default
```
Added value: +10
```
- changedInput schema / properties / limit / description
```
Previous value: -"Number of results (default: 10, max: 20)"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
```
- changedInput schema / properties / query / description
```
Previous value: -"News search query"New value: +"Search query"
```
- 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

A4/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 reasonably well: it discloses result count, returned fields, real-time behavior, and a specific price ($0.005). It does not cover auth requirements, rate limits, or error behavior, but the cost and return-shape disclosure are meaningful behavioral 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?

Two tightly written sentences with zero waste. Purpose, return shape, and cost are all front-loaded.

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 simple two-parameter search tool with full schema coverage and no output schema, the description adequately covers purpose, results, and cost. It could mention whether results are ranked by relevance or recency and any query syntax, but nothing critical is missing for correct invocation.

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 both parameters are fully documented in the schema. The description adds 'up to 10' which aligns with the default but not the maximum of 20, so it adds no new parameter meaning and slightly muddies the limit semantics. Baseline 3 is appropriate.

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?

States a specific verb and resource ('news search via Google News') and clearly distinguishes itself from general web search siblings. The return format is also specified in the same sentence.

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?

The tool name and 'news search' imply when to use it, but there is no explicit guidance on when to prefer it over siblings like search_web or search_discussions. No exclusions or alternatives are named.

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.