Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

The hook + setting libraries, and which hooks are working

list_hooks
Read-onlyIdempotent

Fetch the curated ad hook and setting menu for planning and rendering, with measured traction per hook to select deliberately before and evaluate after publishing.

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.

Input Schema

TableJSON 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, reddit, pinterest)
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.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"
  2. Addedv0.1.161

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false, openWorldHint false), yet the description adds substantial behavioral context: verdict suppression below 5 measured posts with a stated reason, no cross-channel comparison, never-tried hooks reported as fact rather than advice, and the reason unusable hooks are unusable. It closes with 'Read-only, 0 credits.'

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?

Purpose and the before/after call guidance are front-loaded, and each sentence conveys usable behavior. It runs long, with a slightly discursive passage explaining the observation-vs-verdict distinction, but nothing is truly wasted.

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 4 optional parameters, no output schema, and rich annotations already present, the description is complete for correct invocation: it explains what the tool returns conceptually (libraries + measured traction + suppression rules) and how to use it. No output schema means no need to describe return values.

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 tier, channel, category, and authentic in detail. The description reinforces the authentic interaction (on-screen-text hooks unusable for UGC renders) but adds little param syntax beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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: a curated library of hooks (how an ad opens) and settings (where it's staged) plus this brand's measured traction per hook. It names the consuming siblings (plan_ad, render_ad), so an agent can distinguish it from generic library or variant tools without opening a 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?

Gives explicit when-to-use on both sides of the workflow: call before planning an ad to pick a hook deliberately, and after publishing to see which are landing. It also states when-not via the 'three things it will not do' (no thin-data verdicts, no cross-channel comparison, no advice framing).

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