Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Read the market radar

list_watch_findings
Read-onlyIdempotent

Read a brand's MARKET RADAR findings: new ads, 30-day winners with ready briefs, trending formats, top posts, ideas, run state, and next-check quote. Read-only; never triggers a check.

Instructions

Read what a brand's MARKET RADAR (set_competitor_watch) has found: each watched brand's new ads, the winners (ads past 30 days running, with a ready brief to make your own version), the trending formats and top posts for its topics, and the ideas to make, plus its state (lastRun, nextRunAt, lastRunOk, paused) and the quote for its next check. Findings marked seed:true are what a brand was already running at its first check, not new launches. Read-only and free; it never runs a check.

Input Schema

NameRequiredDescriptionDefault
brandNoprofile id/name from list_brands, this call only
limitNomax ads (default 25, max 75)
competitorNoonly this watched brand's ads (exact name as returned)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.454
    • addedInput schema / properties / brand
      Added value: +{
+  "description": "profile id/name from list_brands, this call only",
+  "type": "string"
+}
    • changedInput schema / properties / competitor / description
      Previous value: -"only findings for this watched brand (exact name as returned in `watching`) — omit for all of them"New value: +"only this watched brand's ads (exact name as returned)"
    • changedInput schema / properties / limit / description
      Previous value: -"max findings to return (default 25, max 75 — the server keeps at most 75, and at most 15 per brand)"New value: +"max ads (default 25, max 75)"
  2. Addedv0.1.161

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds valuable behavior: the call is free, it never runs a check, and `seed:true` findings represent pre-existing ads rather than new launches. It also names the state fields returned, going beyond annotation coverage.

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?

Front-loads the core action ('Read what...has found') and then uses the enumeration efficiently; every clause adds substantive return-value or behavioral information. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description comprehensively explains the return shape (ads, winners, trends, posts, ideas, state, quote) and clarifies seed semantics. Combined with full schema coverage, an agent has everything needed to invoke and interpret the tool.

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 all three parameters are documented in the schema, so the baseline is 3. The description does not add syntax or filtering nuance beyond what the schema already provides for brand, limit, and competitor.

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?

Uses a specific verb ('Read') and names the resource ('MARKET RADAR' findings produced by set_competitor_watch), then enumerates exactly what is returned: new ads, winners, trending formats, top posts, ideas, state, and next-check quote. An agent can immediately distinguish this from the setup sibling set_competitor_watch.

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?

Gives clear context for when to call it and an implicit when-not ('it never runs a check'), which steers agents away from using it to refresh data. It does not explicitly route to alternatives such as competitor_teardown or pull_competitor_ads, so it falls short of a full 5.

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