SuprSend

Reset user preferences

users_reset_preferences

DestructiveIdempotent

Resets users' notification preferences to the defaults: the category preferences (the defaults of the categories, or of the tenant) and the channel preferences. It removes every choice that the users made, so tell the user first. To change single categories or channels, use users_set_preferences.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "distinct_ids": "<distinct_ids>",
      "workspace": "<workspace>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "users_reset_preferences"
  }
}

Input Schema

Name	Required	Description
`context`	Yes	Analytics: why you call this tool, in 10-20 words. Say "a user", never names, emails, or IDs.
`channels`	No	Reset the channel preferences (default true). Both false is refused.
`llm_model`	Yes	Analytics: your model ID, or "unknown".
`tenant_id`	No	Reset the preferences in this tenant. Leave it out for the default tenant.
`workspace`	Yes	The slug of the workspace to act on. Call workspaces_list to find the valid values.
`categories`	No	Reset the category preferences (default true).
`distinct_ids`	Yes	The distinct_ids of 1–100 users.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

Name	Required	Description	Default
`success`	No
`_mcp_instructions`	No	Server-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real context: it spells out what is destroyed ('removes every choice that the users made') and the fallback semantics of the reset target ('the defaults of the categories, or of the tenant'). A 4 rather than 5 because it doesn't address scope/auth preconditions or confirmation handling beyond the advisory.

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?

Three short sentences, each earning its place: what it does, the destructive consequence plus warning, and the sibling alternative. Purpose is front-loaded and nothing is padded.

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?

With 8 parameters at full schema coverage, an output schema present, and annotations covering the safety profile, the description supplies exactly the missing pieces an agent needs: destructive consequence, default-resolution semantics, and routing to the non-destructive alternative.

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 coverage is 100% with rich per-parameter descriptions, so the schema carries the parameter burden. The description contributes one extra nuance (category defaults resolve to category-level or tenant-level defaults) but does not clarify the channels/categories booleans or distinct_ids beyond what the schema states.

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?

States a specific verb+resource (resets users' notification preferences to defaults) and enumerates the two dimensions affected (category and channel preferences). It explicitly contrasts itself with the sibling users_set_preferences, so an agent can route without opening schemas.

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?

Names the alternative tool and the condition that selects it ('To change single categories or channels, use users_set_preferences'), and adds a pre-call obligation ('tell the user first') that shapes how the tool should be used. When-to-use and when-not-to-use are both covered.

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

All SuprSend tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.