Skip to main content
Glama

Enroll a contact in a Hive sequence

enroll_contact_in_sequence
DestructiveIdempotent

Put one person into the exact published Hive sequence version they reviewed. Read publishedDocument and currentVersion with read_sequence first. This queues real messages to an eligible person, so your AI asks before this runs; with Hive approvals on, Hive asks again inside Hive. A changed publication requires a new review. Contacts without live consent are recorded as stopped_opt_out and receive no messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contactIdYesThe Hive contact identity to enroll.
sequenceIdYesThe published Hive sequence.
approvalTokenNoSingle-use token returned by Hive after the owner approves this exact action.
entryEventKeyYesA caller-generated key of 8 to 180 characters naming why this person is being enrolled. The same key never enrolls the same person twice.
idempotencyKeyYesA caller-generated unique key (8-200 characters). Reuse it only when retrying this exact write.
expectedVersionYesThe positive currentVersion from read_sequence whose publishedDocument the person reviewed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / expectedVersion
      Added value: +{
      +  "description": "The positive currentVersion from read_sequence whose publishedDocument the person reviewed.",
      +  "type": "integer"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "sequenceId",
      -  "contactId",
      -  "entryEventKey",
      -  "idempotencyKey"
      -]New value: +[
      +  "sequenceId",
      +  "expectedVersion",
      +  "contactId",
      +  "entryEventKey",
      +  "idempotencyKey"
      +]
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources