Courier

subscribe_user_to_lists

Idempotent

Subscribe a user to one or more lists. Creates lists that do not exist.

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": {
      "user_id": "<user_id>",
      "lists": "<lists>"
    },
    "name": "subscribe_user_to_lists"
  }
}

Input Schema

Name	Required	Description	Default
`lists`	Yes	Array of lists to subscribe to
`user_id`	Yes	The user ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already communicate non-read-only and non-destructive behavior, and the description adds a meaningful side effect: missing lists are created. However, it does not clarify behavior for already-subscribed users, partial failures, or the effect of preferences, though idempotentHint does cover some repeat-invocation semantics.

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?

Two short sentences, both earning their place: the first states the core operation, the second discloses an important side effect. There is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple write tool with full parameter documentation, annotations, and no output schema, the description is largely sufficient. The main gap is the lack of guidance distinguishing this plural variant from the singular sibling, which an agent may need when choosing tools.

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 description coverage is 100% and both parameters are documented. The description adds no parameter-specific meaning beyond what the schema already provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: subscribing a user to one or more lists. It also adds a meaningful behavioral detail, 'Creates lists that do not exist.' However, it does not explicitly differentiate itself from the sibling `subscribe_user_to_list` despite their close naming and overlapping purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a use case but gives no guidance on when to use this tool versus siblings like `subscribe_user_to_list`, `bulk_subscribe_to_list`, or `add_subscribers_to_list`. There are no exclusions, conditions, or alternative-selection hints.

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

All Courier 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.