Skip to main content
Glama
Sign In

WebLens

by dev.weblens
OverviewDiscussionsAdmin

search_trends

Google Trends interest over time for a topic, worldwide: a timeline of relative search interest per period (0-100, where 100 is the topic's peak). Use it to see whether interest in a product, technology, brand or keyword is rising, falling or seasonal. Price: $0.04

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

Input Schema

NameRequiredDescriptionDefault
queryYesTopic to get trend data for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / query / example
      Added value: +"cloudflare workers"
    • addedInput schema / properties / query / maxLength
      Added value: +500
    • addedInput schema / properties / query / minLength
      Added value: +1
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does add real context: the 0-100 relative normalization (peak=100), worldwide geographic scope, and an explicit price of $0.04. It omits latency/caching behavior, time-range or granularity limits, and failure modes, 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 sentences, front-loaded with what it returns and its scale, then when to use it, then cost. Every sentence earns its place with no redundancy.

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 no output schema, the description appropriately explains the return value (per-period relative interest scale) and scope. For a single-parameter tool this is nearly sufficient, though it could say more about the time window returned and data resolution.

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% and there is only one parameter, so the schema already documents 'query' fully. The description's mention of product/technology/brand/keyword and worldwide scope adds marginal framing but no syntax, format, or constraint detail beyond the schema.

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+resource ('Google Trends interest over time for a topic') and pins the scope ('worldwide') plus the metric semantics ('timeline of relative search interest per period, 0-100'). This makes it clearly distinguishable from sibling search_web/search_news despite no explicit sibling naming.

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 it to see whether interest in a product, technology, brand or keyword is rising, falling or seasonal' gives a concrete when-to-use with example query domains. It stops short of naming alternatives (e.g. search_web for current results) or stating when this tool is the wrong choice.

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

All WebLens toolsInspect
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.

Resources