Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Draft profile

draft_brand
Destructive

Build a brand profile from a domain, text description, or social handle to generate ad plans; verify the returned name matches the intended brand.

Instructions

Fill in a profile (a business brand or a creator) from a website domain, a free-text description, or a social handle, into a {name, products, logo, …} object you can pass to plan_ad / generate. 0 credits. IMPORTANT: a domain can resolve to a DIFFERENT company than intended (e.g. bala.com is an engineering firm, not the Bala fitness brand at shopbala.com). Before spending any credits on research or renders, VERIFY the returned name (and summary) match the brand the user meant; if it looks wrong, re-draft with the correct domain or a description (pass save:false until confirmed) — this tool cannot ask the user, so the caller owns that check.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveNosave onto the active profile (like Studio onboarding) so plan_ad/create use it automatically. Default: saves only when NO brand is saved yet; pass true to REPLACE the saved profile (the drafted fields overwrite the saved ones), false to never save
domainNoa website to scrape
platformNoplatform for socialHandle (instagram/tiktok/…)
descriptionNoa free-text brand description (no website)
socialHandleNoa social handle to draft from (influencers/creators) — pair with platform

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / save / description
      Previous value: -"save as the workspace’s brand (like Studio onboarding) so plan_ad/create use it automatically. Default: saves only when NO brand is saved yet; pass true to REPLACE the saved brand profile (the drafted fields overwrite the saved ones), false to never save"New value: +"save onto the active profile (like Studio onboarding) so plan_ad/create use it automatically. Default: saves only when NO brand is saved yet; pass true to REPLACE the saved profile (the drafted fields overwrite the saved ones), false to never save"
  2. Changed1 schema field changedv0.1.366
    • changedInput schema / properties / save / description
      Previous value: -"save as the workspace’s brand (like Studio onboarding) so plan_ad/create use it automatically. Default: saves only when NO brand is saved yet; pass true to overwrite, false to never save"New value: +"save as the workspace’s brand (like Studio onboarding) so plan_ad/create use it automatically. Default: saves only when NO brand is saved yet; pass true to REPLACE the saved brand profile (the drafted fields overwrite the saved ones), false to never save"
  3. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "category": {
-      "description": "the detected category",
-      "type": "string"
-    },
-    "domain": {
-      "description": "the brand website domain (empty for non-website drafts)",
-      "type": "string"
-    },
-    "logo": {
-      "description": "the detected logo URL",
-      "type": "string"
-    },
-    "name": {
-      "description": "the drafted brand name — VERIFY it matches the brand the user meant",
-      "type": "string"
-    },
-    "palette": {
-      "description": "the brand colors",
-      "items": {},
-      "type": "array"
-    },
-    "productImages": {
-      "description": "product photo URLs",
-      "items": {},
-      "type": "array"
-    },
-    "products": {
-      "description": "the detected products"
-    },
-    "sells": {
-      "description": "what the brand sells"
-    },
-    "summary": {
-      "description": "a short positioning summary",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (destructiveHint=true, openWorldHint=true, non-idempotent), and the description adds context beyond them: zero credit cost, that it scrapes external sources, that save:true overwrites the saved profile, and that the tool cannot ask the user for confirmation. The destructive/overwrite behavior aligns with destructiveHint rather than contradicting it.

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?

Front-loaded with purpose and cost, then the risk warning, then the remedy. All sentences carry information, though the bala.com/shopbala.com illustration is verbose for the point being made.

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 supplies the return shape, the cost, the verification obligation, and the save semantics — everything needed to call it safely and correctly. Nothing material for correct invocation is missing.

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 description coverage is 100%, so the baseline is 3; the description goes further by tying save:false to the verification workflow and by warning that a domain may resolve to a different company, which changes how the agent should choose the domain vs description parameter. It does not add much beyond the schema for platform/socialHandle.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (draft/fill in) and resource (a brand/creator profile), and names the output shape ({name, products, logo, …}) plus the downstream consumers plan_ad and generate. It does not explicitly contrast itself with the sibling brand tools (create_brand, update_brand, get_brand), so an agent must infer the 'draft vs persist' distinction from the save parameter.

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?

Explicit about when to use it (before spending credits on research or renders), what to do when the result looks wrong (re-draft with correct domain or a description, pass save:false until confirmed), and who owns the verification step. This is exactly the when/when-not/alternative guidance the dimension asks for.

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