Skip to main content
Glama
Sign In

Zenserp MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Search Google News

zenserp_news_search
Destructive

Google News results for a query: title, source, date, snippet. SPENDS 1 request of the monthly quota per successful call (failed calls are not charged); do not repeat a call needlessly. GET /v2/search (tbm=nws).

Input Schema

NameRequiredDescriptionDefault
qYesThe query.
glNoCountry (gl), two letters, e.g. us, de, gb. zenserp_list_countries lists the supported codes. Default: United States.
hlNoInterface language (hl), e.g. en, de, pt-BR. zenserp_list_languages lists the supported codes.
lrNoLimit results to these languages (lr), prefixed with lang_ and joined by |, e.g. lang_fr.
tbsNoGoogle 'tbs' filter string for what the query field cannot express, e.g. qdr:w (past week).
cacheNotrue = serve a stored copy when one exists (kept 24 h, NOT charged) and store the reply when not. Default false: every call is fetched live and charged.
startNoResult offset: 0 (default) first page, 10 second page, 20 third page ... Google serves about 300 results per query.
deviceNoDevice to emulate.
fieldsNoOnly return these top-level keys of the reply (for example organic, paid_results, related_searches). Saves context; the call is charged the same.
locationNoGeolocation of the search, in Google's canonical form, e.g. 'Manhattan,New York,United States' (see zenserp_search_locations). Set it when the result depends on place, especially ads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The description meaningfully exceeds annotations by disclosing the quota cost model ('SPENDS 1 request of the monthly quota per successful call; failed calls are not charged') and the endpoint protocol (GET /v2/search with tbm=nws). However, it contradicts the destructiveHint=false implication of a read-only search, and it doesn't mention caching or pagination behavior covered elsewhere.

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 tightly packed sentences with zero waste: purpose, behavioral constraint, and protocol details are all front-loaded. Every phrase carries specific 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 10-parameter search tool with full schema coverage and no output schema, the description covers the essential behavioral context: quota cost, caching implications, and endpoint. It doesn't explicitly state the return format, but the schema and query behavior are well-described.

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 the schema already documents all 10 parameters thoroughly. The description adds no parameter-level details beyond what the schema provides, which is acceptable given the high coverage.

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 states a specific verb and resource: 'Google News results for a query' with enumerated return fields (title, source, date, snippet). It doesn't explicitly distinguish from siblings such as zenserp_search or zenserp_video_search, but the 'News' qualifier implies the distinction.

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 description implies usage through the quota warning ('do not repeat a call needlessly'), but gives no explicit when-to-use or when-not-to-use guidance relative to sibling tools. The context of search types is left to the agent to infer from the tool name.

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

All Zenserp MCP by usefulapi 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