Skip to main content
Glama

upsert_suprsend_user

Destructive

Upsert a SuprSend user by setting properties or managing delivery channels. Perform one action per call: set, unset, append, increment, add/remove channel identifiers.

Instructions

Modify properties or channel identifiers on a SuprSend user. One call performs ONE action; for multiple changes, call this tool multiple times.

Actions:

  • set, set_once, unset, remove — modify a scalar property by key/value. remove permanently deletes the key.

  • append, increment — modify array / numeric values.

  • set_preferred_language, set_timezone — locale and timezone on the user.

  • add_email / remove_email, add_sms / remove_sms, add_whatsapp / remove_whatsapp, add_androidpush / remove_androidpush, add_iospush / remove_iospush, add_slack / remove_slack — register or deregister a delivery channel.

Channel registration is special. For channel identifiers ALWAYS use the dedicated add_ / remove_ actions — generic set / unset will not register the channel correctly with the delivery router. Slack additionally requires the slack_details payload alongside the action.

When to use: creating a new user or modifying an existing user's stored state.

When NOT to use:

  • For non-user entities — use upsert_suprsend_object.

  • For preferences — use update_suprsend_users_preferences (per category) or update_suprsend_user_channel_preference (across categories).

  • For tenant settings — use upsert_suprsend_tenant.

Side effects: remove and unset permanently delete data. add_ makes the user reachable on that channel for any future workflow run; remove_ stops delivery immediately.

Returns: the updated user on success; structured error with field reasons on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action to perform. use action "upsert" to create a new user or update an existing user's properties. use action "remove" to remove a user's properties. use action "set" to set a user's property, don't use this when trying to add email, add sms, add whatsapp, add androidpush, add iospush, add slack use the respective actions. use action "unset" to unset a user's property, don't use this when trying to remove email, remove sms, remove whatsapp, remove androidpush, remove iospush, remove slack use the respective actions. use action "set_once" to set a user's property once, this will only set the property if it is not already set. use action "append" to append a value to a user's property. use action "increment" to increment a user's property. use action "add_email" to add an email to a user. use action "remove_email" to remove an email from a user. use action "add_sms" to add an SMS to a user. use action "remove_sms" to remove an SMS from a user. use action "add_whatsapp" to add a WhatsApp to a user. use action "remove_whatsapp" to remove a WhatsApp from a user. use action "add_androidpush" to add an Android push to a user. use action "remove_androidpush" to remove an Android push from a user. use action "add_iospush" to add an iOS push to a user. use action "remove_iospush" to remove an iOS push from a user. use action "add_slack" to add a Slack to a user. use action "remove_slack" to remove a Slack from a user. use action "set_preferred_language" to set a user's preferred language. use action "set_timezone" to set a user's timezone.
distinct_idYesThe distinct_id of the user to get.
keyNoThe key on which the action is to be performed. only required for set, append, increment, unset actions.
ms_teams_detailsNoThis is only applicable for add_ms_teams and remove_ms_teams actions.
slack_detailsNoThis is only applicable for add_slack and remove_slack actions.
valueNoThe value to needs to be added/removed/set/unset/appended/incremented.
webpush_detailsNoThis is only applicable for add_webpush and remove_webpush actions.
workspaceNoSuprSend workspace to get the user from.
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds behavioral details: remove/unset permanently delete data, add_<channel> makes user reachable, remove_<channel> stops delivery immediately. These provide useful context beyond annotations, though it could mention rate limits or auth requirements.

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?

Well-structured with a clear summary, sections for actions, usage guidance, and side effects. Every sentence adds value without redundancy. Front-loaded with the core purpose.

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?

Given the tool's complexity (8 params, no output schema), the description covers purpose, usage guidelines, action details, side effects, and return value. It is thorough for an agent to correctly select and invoke the tool.

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 baseline is 3. The description adds value by grouping actions and explaining their effects, but the schema already fully describes each parameter. The additional context is helpful but not essential.

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?

The description clearly states it modifies properties or channel identifiers on a SuprSend user, using a specific verb and resource. It distinguishes from sibling tools like upsert_suprsend_object and update_suprsend_users_preferences by specifying when not to use them.

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?

Explicitly states when to use (creating or modifying a user) and when NOT to use, listing alternative tools for non-user entities, preferences, and tenant settings. Also warns that channel registration requires dedicated actions, not generic set/unset.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/suprsend/cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server