Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Update a saved creator (outreach status, note)

update_saved_creator
DestructiveIdempotent

Set outreach status (new, contacted, replied, booked, passed) and add notes for a creator saved in your swipefile. Returns the updated row.

Instructions

Set the OUTREACH STATUS and/or a NOTE on a creator already saved in the swipefile (find_creators -> save_to_swipefile, or the heart on a creator card). Status is one of new | contacted | replied | booked | passed. The note is free text (deal terms, rate, what was sent). Reads back the updated row. Use list_swipefile to find the key. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesthe saved row's key from list_swipefile, e.g. tiktok:handle
noteNoreplaces the existing note; pass "" to clear it
brandNoprofile id/name from list_brands, this call only
statusNo

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.209

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the mutation/destructive/idempotent profile, so the bar is lower; the description adds real value beyond them by stating 'Reads back the updated row' (return behavior) and 'Free' (no cost). It does not spell out that overwriting a note is the destructive action, but that is covered in the schema text.

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-loads the core action and status enum, then adds the key-finding tip and cost note. Every sentence carries information, though the workflow parenthetical and the 'Free' note make it slightly denser than strictly necessary.

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 4-param mutation tool with no output schema, the description covers the action, the status vocabulary, note purpose, key provenance, and the return behavior ('reads back the updated row'). Coverage is solid; only the brand parameter and the destructive effect of note replacement are left implicit.

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 75%, and the description still enriches it: it enumerates the valid status values and clarifies the note's intended use ('deal terms, rate, what was sent'). It omits the 'brand' parameter entirely, leaving only the schema description to cover that last quarter.

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 ('Set') and resource ('outreach status and/or note on a creator already saved in the swipefile'), with a parenthetical workflow hint (find_creators -> save_to_swipefile, or the heart). An agent can distinguish it from siblings like save_creator, save_to_swipefile, or update_brand 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 Guidelines4/5

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

Gives a clear prerequisite/routing instruction: 'Use list_swipefile to find the key', and ties the tool to the save flow. It lacks explicit when-not guidance (e.g. how it differs from save_creator for brand-new creators), but the context needed to use it is present.

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