Skip to main content
Glama

add_suprsend_object_subscriptions

Destructive

Subscribe users or objects to a specific object. Pass recipients as a mix of user distinct_ids and object identifiers.

Instructions

Subscribe one or more users or other objects TO this object. The recipient list can mix users and objects in a single call.

Recipients: users by distinct_id, objects by object_type + id. Each entry's shape follows the SuprSend recipient format. Optional properties attach metadata to each subscription (role, joined_at, etc.).

When NOT to use:

  • To remove subscribers — there is no remove tool; use the SuprSend API directly.

  • For mailing-list / segment membership — those are managed via the Lists API.

  • For preference changes on existing subscribers — use the per-user / per-object preference tools.

Side effects: each successful subscription is a separate row. Calling this twice with the same recipient creates duplicate-looking entries; check existing state with get_suprsend_object_subscriptions first if duplicates would be a problem.

Returns: the created subscription records on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_idYesThe object_id of the object's subscriptions to get.
workspaceNoSuprsend workspace to get the object from.
propertiesNoProperties of an user/object
recipientsYesUsers & Objects who are subscribing to an object
object_typeYesThe type of object you want to get.
Behavior5/5

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

Discloses side effects (duplicate entries on repeated calls), suggests checking existing state, and notes return value. Annotations already indicate destructive=true and non-idempotent, and description adds useful context beyond annotations.

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?

Concise, front-loaded with purpose, then recipients, usage restrictions, and side effects. Every sentence contributes meaningfully.

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?

Despite no output schema, the description states return value. Covers usage, side effects, and parameter details thoroughly for a moderately complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description still adds value by explaining recipient format (distinct_id vs object_type+id), optional metadata via properties, and references SuprSend recipient format.

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 the tool subscribes users/objects to an object, specifying verb and resource. It differentiates from sibling tools like get_suprsend_object_subscriptions and lists when not to use.

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 provides when-not-to-use scenarios and alternative tools (SuprSend API, Lists API, preference tools), giving clear guidance on tool selection.

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