Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Save a skill

save_skill

Store reusable custom creative directives, playbooks, hooks, or compliance rules in your Skills library so future ads apply them consistently.

Instructions

Save a reusable custom SKILL — a named creative directive/playbook applied to future ads (a hook formula, a UGC recipe, a compliance rule, a named specialist persona like “our founder-story style” or “short-form ad strategist”). Distill an imperative, self-contained directive. Merges into the workspace Skills library (list_skills shows built-ins + your custom skills).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesshort skill name, e.g. “Founder-story hook”
brandNoprofile id/name from list_brands, this call only
directiveYesthe full instruction the skill applies when used (1–6 sentences, imperative)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"brand id/name from list_brands, this call only"New value: +"profile id/name from list_brands, this call only"
  2. Changed1 schema field changedv0.1.371
    • addedInput schema / properties / brand
      Added value: +{
+  "description": "brand id/name from list_brands, this call only",
+  "type": "string"
+}
  3. Addedv0.1.161

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the safety burden is partly lifted. The description adds real context beyond that: it explains the effect is a merge into the workspace Skills library (additive, not a wholesale overwrite) and routes the agent to list_skills. It does not clarify what happens on a same-name repeat call, which idempotentHint=false makes relevant.

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 is front-loaded in the first clause with the parenthetical examples earning their place by disambiguating the concept. It is slightly dense with em-dashes but contains no filler sentences.

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?

For a 3-parameter save tool with full schema coverage, no output schema (and none needed), and annotations covering safety, the description supplies the concept, the effect, and a related sibling. The only gap is same-name/idempotency behavior, which is minor given the overall completeness.

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 the schema already documents all three parameters (name, brand, directive) with examples. The description reinforces the expected form of the directive (imperative, self-contained) but adds little syntax or format detail beyond what the schema states, so 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?

States a specific verb+resource ("Save a reusable custom SKILL") and defines what a skill is with concrete examples (hook formula, UGC recipe, compliance rule, persona). This clearly distinguishes it from siblings like get_skill, list_skills, and delete_skill 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 Guidelines3/5

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

Implies usage (creating a reusable directive for future ads) and gives a formulation hint ("Distill an imperative, self-contained directive"), and references list_skills as the inspection counterpart. However, it never explicitly states when to prefer this over siblings like save_playbook or remember, nor any prerequisites or exclusions.

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