WebLens

search_images

Google Images search. Returns direct image URLs with dimensions, thumbnails, and source pages. 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_images"
  }
}

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: -"Image 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

A3.8/5.0

Behavior4/5

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

With no annotations, the description does real work: it discloses the return contents (direct image URLs with dimensions, thumbnails, and source pages) and the cost ($0.005). It stops short of auth/rate-limit details, keeping it just below a full 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 short sentences, front-loaded with purpose, then return value, then cost. No filler; every sentence carries 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 two-parameter search tool with full schema coverage, the description covers purpose, return shape (important since there is no output schema), and cost. Only usage framing is missing, which is minor here.

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 both query and limit are documented in the schema already. The description adds no syntax or constraint detail beyond that, so the baseline 3 applies.

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 (search) and resource (Google Images), which clearly distinguishes it from siblings like search_web, search_news, and search_shopping. The agent can tell what it does without opening the schema.

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

Usage Guidelines2/5

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

No guidance on when to use this over image-adjacent alternatives, no prerequisites, and no exclusions. The intent (find images) is implied by the name but never stated as a use case.

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.