Skip to main content
Glama

update_suprsend_tenant_default_preference

DestructiveIdempotent

Set the default notification category preference for new tenant users, including opt-in/out status, mandatory and blocked channels, and subscriber visibility.

Instructions

Set the default category preference inherited by NEW users created in this tenant. Existing users are not affected; their preferences are independent.

preference values:

  • opt_in — new users are opted into this category.

  • opt_out — new users are opted out.

  • cant_unsubscribe — new users are opted in AND locked from toggling.

mandatory_channels — channels users cannot disable for this category. blocked_channels — channels that cannot be enabled. visible_to_subscriber — whether end-users see this category in their preference UI.

When NOT to use:

  • For per-user overrides — use update_suprsend_users_preferences.

  • For per-object overrides — use update_suprsend_category_preference_object.

Side effects: changes apply only to users created AFTER this call. To retroactively update existing users, call update_suprsend_users_preferences per user.

Returns: the updated tenant default preference on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blocked_channelsYesThe channels to block for the category.
categoryYescategory_slug of an category to update.
mandatory_channelsYesThe channels to make mandatory for the category.
preferenceYesThe preference to update for the tenant.
tenant_idYesThe tenant_id of the tenant to update.
visible_to_subscriberYesWhether the category is visible to subscribers.
workspaceNoSuprSend workspace to update the tenant from.
Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. The description adds critical context: the effect is only on new users, not retroactive, and that existing users are unaffected. This goes beyond annotations to describe scope and side effects.

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?

The description is concise and well-structured: purpose, parameter values, when-not-to-use, side effects, return. Every sentence is informative without redundancy.

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 (7 parameters, no output schema), the description fully covers its purpose, usage context, parameter semantics, side effects, and return value. It is complete for an agent to select and invoke correctly.

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?

All parameters are documented in the schema (100% coverage). The description adds extra meaning by explaining the role of parameters like 'mandatory_channels' and 'blocked_channels', and the allowed enum values for preference.

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 specifies that the tool sets the default category preference for new users in a tenant, using clear verbs and resource. It explicitly distinguishes from sibling tools like 'update_suprsend_users_preferences' and 'update_suprsend_category_preference_object'.

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?

The description provides explicit when-not-to-use guidance, naming alternative tools for per-user and per-object overrides. It also explains that changes only apply to new users, helping the agent decide between this and other tools.

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