Skip to main content
Glama

update_suprsend_tenant_default_preference

DestructiveIdempotent

Sets the default category preference inherited by new users created in a tenant. Existing users are not affected.

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
categoryYescategory_slug of an category to update.
tenant_idYesThe tenant_id of the tenant to update.
workspaceNoSuprSend workspace to update the tenant from.
preferenceYesThe preference to update for the tenant.
blocked_channelsYesThe channels to block for the category.
mandatory_channelsYesThe channels to make mandatory for the category.
visible_to_subscriberYesWhether the category is visible to subscribers.
Behavior5/5

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

The description adds context beyond annotations by explaining the side effect that changes apply only to new users, not existing ones. This clarifies the 'destructiveHint: true' annotation (changes are not destructive to existing data). It also describes the return value on success.

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

Conciseness4/5

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

The description is well-structured with front-loaded purpose, clear separate sections for preference values and usage guidance. It is slightly long but every sentence earns its place, providing necessary detail 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 complexity (7 parameters, no output schema), the description covers purpose, side effects, alternatives, returns, and parameter explanations. It is fully sufficient for an agent to select and invoke this tool 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?

With 100% schema coverage, the baseline is 3. The description adds value by explaining the meaning of preference values (opt_in, opt_out, cant_unsubscribe) and the roles of mandatory_channels, blocked_channels, and visible_to_subscriber. This enriches the schema's descriptions.

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's purpose using a specific verb ('Set the default category preference inherited by NEW users') and resource ('tenant'). It distinguishes from sibling tools by emphasizing the scope (new users only) and mentions alternatives.

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 explicitly provides when NOT to use the tool ('For per-user overrides' and 'For per-object overrides') and names the exact alternative tools (update_suprsend_users_preferences, update_suprsend_category_preference_object). This gives clear guidance to the agent.

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