Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Google ads

search_google_ads

Fetch structured Google Ads Transparency data for one advertiser by domain or advertiser ID. Returns compact JSON for each ad, including ad URL, image, and first/last shown dates.

Instructions

Structured Google Ads Transparency pull for ONE advertiser (by domain or advertiserId) — use when you know the brand; use research_ads for open-ended research. Deliberately fetches the cheap BASIC listing (get_ad_details=false, ~1 credit — the detailed variant with per-ad headlines costs 25 credits/call and is not exposed here). Returns compact JSON {advertiser, format, adUrl, image, firstShown, lastShown} per ad.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomax ads returned (1–25, default 8)
domainNothe advertiser's domain, e.g. nike.com
regionNo2-letter region, default US
advertiserIdNoGoogle advertiser id (AR…) when the domain is ambiguous

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "ads": {
-      "description": "the compact ad objects ({advertiser, format, adUrl, image, firstShown, lastShown})",
-      "items": {},
-      "type": "array"
-    },
-    "found": {
-      "description": "total ads found upstream",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior1/5

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

The description frames the tool as a retrieval operation ('pull', 'fetches', 'Returns compact JSON'), but the annotations declare readOnlyHint=false. That structured signal says the tool is not read-only, which contradicts the description's fetch/search framing. The useful cost disclosure (~1 credit, no 25-credit detailed variant) does not resolve this contradiction.

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?

The description is dense but front-loaded: purpose and alternative first, then cost behavior, then return shape. Every sentence carries useful selection or invocation information, with no filler.

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?

It gives the return fields, the cost model, and the sibling alternative, which is strong for a search tool with no output schema. The remaining gap is that it does not reconcile the read-only framing with the annotation readOnlyHint=false.

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 domain, advertiserId, limit, and region are already documented. The description only repeats the domain/advertiserId distinction and adds no syntax or default behavior beyond the schema, so 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 ('Structured Google Ads Transparency pull for ONE advertiser') and scopes it to domain or advertiserId. It also explicitly distinguishes itself from research_ads for open-ended research, so an agent can select it without opening another schema.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('when you know the brand') and names the alternative for the opposite case ('use research_ads for open-ended research'). This is exactly the when/when-not routing guidance an agent needs.

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

Deploy Server

Other Tools