Skip to main content
Glama
Hermoso

Hermoso

Official

The hook + setting libraries, and which hooks are working

list_hooks
Read-onlyIdempotent

Retrieve curated ad hooks and settings with measured traction before planning or after publishing, so you can choose deliberately and see which hooks land.

Instructions

The curated menu of VISUAL scroll-stop HOOKS (how an ad opens) and SETTINGS (where it is staged) that plan_ad and render_ad accept, PLUS this brand's measured traction per hook. Call it before planning an ad to pick a hook deliberately instead of letting the model improvise one, and call it after publishing to see which ones are actually landing. Three things it will not do: it never recommends a hook from thin data — a verdict is SUPPRESSED below 5 measured posts and the reason is stated; it never compares across channels; and it reports hooks you have NEVER TRIED as a fact, not as advice, because 'you haven't tried this' is an observation and 'you should' would be a verdict drawn from zero data. A hook marked unusable in this brief says WHY (an on-screen-text hook cannot ride an authentic/UGC render, which carries zero on-screen text). Read-only, 0 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_hooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoproduct tier, used with category — changes the FINISH of the room, never the room. Default premium.
channelNorestrict the performance half to one channel (facebook, instagram, threads, x, linkedin, youtube, tiktok, pinterest, bluesky)
categoryNothe product category (e.g. 'skincare serum', 'protein powder', 'sunglasses') — returns the setting our Location x Tier matrix puts that category in, with the reason
authenticNotrue if the planned ad is an authentic/UGC/creator-register render — on-screen-text hooks are then reported unusable, with the reason

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.519
    • changedInput schema / properties / channel / description
      Previous value: -"restrict the performance half to one channel (facebook, instagram, threads, x, linkedin, youtube, tiktok, reddit, pinterest)"New value: +"restrict the performance half to one channel (facebook, instagram, threads, x, linkedin, youtube, tiktok, pinterest, bluesky)"
  2. Changed1 schema field changedv0.1.162
    • changedInput schema / properties / category / description
      Previous value: -"the product category (e.g. 'skincare serum', 'protein powder', 'sunglasses') — returns the setting Higgsfield's Location x Tier matrix puts that category in, with the reason"New value: +"the product category (e.g. 'skincare serum', 'protein powder', 'sunglasses') — returns the setting our Location x Tier matrix puts that category in, with the reason"
  3. Addedv0.1.161

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for going further: a hard suppression rule below 5 measured posts with the reason stated, a no-cross-channel-comparison limit, untried hooks reported as observation rather than advice, and explicit reasons when a hook is marked unusable for an authentic/UGC render. The '0 credits' note adds cost information annotations do not carry.

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

Conciseness3/5

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

Core information is front-loaded in the first sentence, but the 'three things it will not do' section drifts into justification prose ('an observation and "you should" would be a verdict drawn from zero data') that restates the same point rather than adding usable detail. Tighter phrasing would preserve the constraints without the digression.

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 four optional parameters, full schema coverage, and no output schema, the description is nearly complete: it says what is returned (library plus per-hook traction, with suppressions and unusable flags) and how to use it in the workflow. It stops short of describing the response shape or library size, which would help given there is no output schema.

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 coverage is 100%, so each parameter's meaning is already documented, including the authentic flag's effect on on-screen-text hooks. The description reinforces the channel scoping and the authentic-render consequence, but adds little syntax or semantics the schema does not already state — baseline 3 applies.

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?

The description names both resources it returns — the hook/setting library that plan_ad and render_ad consume, plus this brand's measured traction per hook — and explicitly frames itself as the reference consulted before planning. An agent can distinguish it from plan_ad, render_ad, and hook_variants without opening any 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?

It gives two explicit invocation points: before planning an ad (to choose a hook deliberately rather than improvise) and after publishing (to see which hooks land). It also carves out boundaries — no cross-channel comparison, no recommendation from thin data — which functions as when-not guidance.

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