Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Mine customer angles

mine_angles

Mine ad angles from real customer language: gather reviews and social posts, then get a ranked bank of angles with verbatim proof quotes, scores, and ready-to-run hooks.

Instructions

Mine ad ANGLES from real customer language: gathers the customer's own words (Reddit, TikTok, the brand's review page + review-site results) and returns a RANKED angle bank — each angle tagged (pain / outcome / identity / fear / competitive-displacement / social-proof / contrast), 2-5 VERBATIM proof quotes, a 0-100 score with breakdown, and a ready-to-run hook in the customer's own voice. Reads YOUR saved brand (pass brandId to target a specific profile — that switches this key's active profile like use_brand). To tear down a COMPETITOR use competitor_teardown instead. YOUR OWN REVIEWS: pass reviews (a list of review texts, or one pasted block: one per line, numbered, blank-line separated, or a CSV with a review column) and/or reviewsUrl (a CSV, TXT or JSON file from upload_file, or a review page; on a local CLI a file path works too). They are first-class evidence: every quote from them is checked word for word against what you sent and labelled 'your reviews', and a quote that is not verbatim is dropped and counted. useOwnReviewsOnly:true mines only your reviews and gathers nothing public. Limits: 300 reviews, 2,000 characters each, 40,000 in total; over that it is refused at no cost, so send fewer or split into batches. Each angle comes back with next: the exact plan_variations and generate_image arguments that turn it into finished statics (one generate_image per angle = statics with distinct angles). Spends a few credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandIdNoa profile id/name from list_brands to mine for; omit to use the active profile
reviewsNoyour own customer reviews: a list of review texts, or one pasted block (one per line, numbered, blank-line separated, or CSV with a review column)
reviewsUrlNoa URL of your reviews: an uploaded CSV, TXT or JSON file (from upload_file) or a review page. On a local CLI a file path also works.
useOwnReviewsOnlyNotrue = mine only your reviews, no public search (no search credits). Default false = merge with public customer language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brandId / description
      Previous value: -"a brand id/name from list_brands to mine for; omit to use the active brand"New value: +"a profile id/name from list_brands to mine for; omit to use the active profile"
  2. Changed3 schema fields changedv0.1.272
    • addedInput schema / properties / reviews
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "your own customer reviews: a list of review texts, or one pasted block (one per line, numbered, blank-line separated, or CSV with a review column)"
+}
    • addedInput schema / properties / reviewsUrl
      Added value: +{
+  "description": "a URL of your reviews: an uploaded CSV, TXT or JSON file (from upload_file) or a review page. On a local CLI a file path also works.",
+  "type": "string"
+}
    • addedInput schema / properties / useOwnReviewsOnly
      Added value: +{
+  "description": "true = mine only your reviews, no public search (no search credits). Default false = merge with public customer language.",
+  "type": "boolean"
+}
  3. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "angles": {
-      "description": "the ranked angle bank ({category, angle, score, hook_draft, proof_quotes})",
-      "items": {},
-      "type": "array"
-    },
-    "note": {
-      "description": "why no angles were returned, when the bank is empty",
-      "type": "string"
-    },
-    "sourceCount": {
-      "description": "how many customer sources were mined",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare it is a non-read-only, open-world, non-idempotent, non-destructive operation; the description adds the substantive traits: it reads YOUR saved brand, silently switches the active profile, spends credits, enforces review-size limits, and drops/counts non-verbatim quotes. This is far more than the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core purpose and the key alternative are front-loaded, and every sentence carries operational detail. It is dense and long with some repetition of the reviews/reviewsUrl mechanics, but nothing is purely filler, so it is efficient rather than padded.

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?

With no output schema, the description fully covers the return shape (ranked angles, tags, 2-5 verbatim quotes, 0-100 score, hook, and the `next` plan_variations/generate_image arguments). Combined with the disclosed limits and cost behavior, an agent has everything needed to invoke and interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: accepted review formats (list, numbered lines, blank-line separated, CSV column), accepted reviewsUrl formats (CSV/TXT/JSON from upload_file, page, or local path), and the behavioral effect of useOwnReviewsOnly. It does not add much on brandId beyond the schema, keeping it just above baseline.

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 ('Mine ad ANGLES from real customer language') and details the output artifact (a ranked angle bank with tagged angles, verbatim quotes, scores, and hooks). It explicitly distinguishes itself from the sibling competitor_teardown and references use_brand/list_brands, so an agent can route correctly without opening schemas.

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?

Gives explicit when-to-use (mine customer language from Reddit, TikTok, reviews), when-not (tear down a competitor -> competitor_teardown), and alternative mechanisms (pass brandId to switch the active profile like use_brand; useOwnReviewsOnly to skip public gathering). Hard limits are stated with the exact fallback (refused at no cost, so send fewer or split into batches).

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