Skip to main content
Glama
Hermoso

Hermoso

Official

Update a saved creator (outreach status, note)

update_saved_creator
DestructiveIdempotent

Update a saved creator's outreach status and add or replace a note with deal terms; returns the updated swipefile 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "update_saved_creator"
  }
}

Input 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
statusNooutreach status: new, contacted, replied, booked or passed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.465
    • addedInput schema / properties / status / description
      Added value: +"outreach status: new, contacted, replied, booked or passed"
  2. 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"
  3. Changed1 schema field changedv0.1.371
    • addedInput schema / properties / brand
      Added value: +{
      +  "description": "brand id/name from list_brands, this call only",
      +  "type": "string"
      +}
  4. Addedv0.1.209

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation profile is covered structurally. The description adds genuinely useful non-schema facts — 'Free' and 'Reads back the updated row' — but says nothing about what destruction actually means here (the destructive hint is really just a note replacement) or any permission/auth requirement.

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

Conciseness5/5

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

Front-loaded with the action and resource, then flow, then enum, then the lookup cue — all in four tight sentences with no filler. Even the trailing 'Free.' earns its place as a cost signal.

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 full schema coverage, existing annotations and no output schema, the description covers purpose, prerequisite, allowed values and return behavior. Only gap is the absence of any partial-update/omission semantics narrative beyond what the schema sentences carry.

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 baseline is 3. The description repeats the enum values already enumerated in the schema and gives flavor for note content ('deal terms, rate, what was sent') but adds no semantics beyond what the fields already state.

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 — set outreach status and/or note on an already-saved creator — and scopes it to the swipefile. The phrase 'a creator already saved in the swipefile' cleanly separates it from save_creator / save_to_swipefile siblings.

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 the discovery prerequisite explicitly ('Use list_swipefile to find the key') and traces the upstream flow (find_creators -> save_to_swipefile, or the heart on a creator card). It stops short of naming when NOT to use it (e.g. delete_creator for removal), so not a full 5.

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