Skip to main content
Glama
Sign In

SuprSend

by com.suprsend
OverviewDiscussionsAdmin

Add users to a list

lists_add_users
Idempotent

Adds users to a static subscriber list, by distinct_id, up to 10,000 per call. Only users that exist are added (create others first with users_upsert); users in the list already stay, so a call is safe to repeat. With a version_id, the users go into the draft of a replace (lists_start_replace). Dynamic lists cannot be changed: their query decides the members. If the list tracks entries, workflows that listen for them start and can send notifications.

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": {
      "list_id": "<list_id>",
      "distinct_ids": "<distinct_ids>",
      "workspace": "<workspace>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "lists_add_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesAnalytics: why you call this tool, in 10-20 words. Say "a user", never names, emails, or IDs.
list_idYesThe list ID (see lists_list).
llm_modelYesAnalytics: your model ID, or "unknown".
workspaceYesThe slug of the workspace to act on. Call workspaces_list to find the valid values.
version_idNoThe draft from lists_start_replace: the users go into the draft, and the live list does not change until lists_finish_replace. Leave it out to change the live list.
distinct_idsYesThe distinct_ids of the users, 1–10,000. For more, call again with the next ones.
conversation_idNoPass 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it explains why the call is repeatable (existing members stay), discloses downstream side effects (workflows listening for entries start and can send notifications), and clarifies that version_id targets a draft while omitting it changes the live list. The idempotency claim corroborates idempotentHint=true and adds the reason.

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 core action and scope are front-loaded in the first sentence, and each subsequent sentence covers a distinct concern (prerequisites, idempotency, draft routing, dynamic-list exclusion, side effects) with no filler.

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?

No output schema exists, but for a mutating tool with side effects the description covers prerequisites, idempotency, constraints, draft-vs-live behavior, and notification consequences. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description reinforces the meaning of distinct_ids (batch size, distinct_id keying) and frames version_id within the replace workflow. It adds contextual meaning rather than raw format detail already in the schema.

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 and resource (adds users to a static subscriber list) plus the keying mechanism (by distinct_id) and the batch limit. It distinguishes itself from siblings by ruling out dynamic lists and pointing to users_upsert and lists_start_replace for adjacent needs, so an agent can place it precisely among the many list tools.

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?

Gives explicit prerequisites (only existing users are added; create others first with users_upsert), an exclusion (dynamic lists cannot be changed), and an alternative path (version_id routes into the draft of a replace). When-to-use and when-not-to-use are both spelled out.

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

All SuprSend toolsInspect
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.

Resources