Skip to main content
Glama
Sign In

MailSenpai

by com.mailsenpai
OverviewDiscussionsAdmin

Confirm Subscriber by UID

confirm_subscriber
Destructive

Sets a subscriber's status to confirmed by subscriber_uid: confirms an unconfirmed contact or re-subscribes one who unsubscribed, so they receive campaigns again. Do this only with the contact's consent and after the user confirms. Use confirm_subscriber_by_email if you only have the address.

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_uid": "<list_uid>",
      "subscriber_uid": "<subscriber_uid>"
    },
    "name": "confirm_subscriber"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoOptional extra subscriber fields to save in the same call, keyed by field tag, e.g. {"FNAME": "Jane"}. Usually omitted.
list_uidYesUnique ID of the mailing list (list_uid), a 13-character code such as "ab123cd456ef7". Find it with list_lists.
subscriber_uidYesUnique ID of the subscriber (subscriber_uid), a 13-character code. Find it with search_subscriber_by_email or list_subscribers.

Output Schema

NameRequiredDescriptionDefault
okNoWhether the MailSenpai MCP operation succeeded.
dataNoMain MailSenpai API response payload, when available.
errorNoMachine-readable error name when the tool fails.
resultNoAlternative result payload for tools that return a named result.
statusNoStatus returned by MailSenpai or by the MCP layer.
detailsNoAdditional diagnostic details, validation errors, API response body or nested metadata.
messageNoHuman-readable message from MailSenpai or from the MCP layer.
paginationNoPagination metadata for list/search tools when returned by the MailSenpai API.
rate_limitNoRate-limit metadata when relevant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / data / description
      Added value: +"Optional extra subscriber fields to save in the same call, keyed by field tag, e.g. {\"FNAME\": \"Jane\"}. Usually omitted."
    • addedInput schema / properties / list_uid / description
      Added value: +"Unique ID of the mailing list (list_uid), a 13-character code such as \"ab123cd456ef7\". Find it with list_lists."
    • addedInput schema / properties / subscriber_uid / description
      Added value: +"Unique ID of the subscriber (subscriber_uid), a 13-character code. Find it with search_subscriber_by_email or list_subscribers."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the safety profile is covered. The description still adds real value beyond that: it discloses the state transition that an unsubscribed contact will start receiving campaigns again, and imposes a consent precondition. It does not discuss idempotency behavior or partial failure, which is the only remaining gap.

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?

Three compact sentences, front-loaded with the effect and then the consent rule and the alternative. Every sentence earns its place, though the two clauses of the first sentence could be tightened slightly.

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?

An output schema exists, so return values need no explanation. For a single-entity status mutation with previously-flagged safety annotations, the description covers purpose, the resulting state change, the consent prerequisite, and the email-based alternative — nothing an agent needs to call it correctly is missing.

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%, so all three parameters (including the optional data bag) are already documented in the schema, establishing a baseline of 3. The description adds no syntax, format, or constraint details about any parameter 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 (sets status to confirmed) plus the resource (subscriber, keyed by subscriber_uid), and unpacks the two distinct outcomes: confirming an unconfirmed contact and re-subscribing an unsubscribed one. It also names the sibling confirm_subscriber_by_email, so an agent can distinguish them without opening either schema.

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?

Explicit when-to-use ('only with the contact's consent and after the user confirms') and an explicit alternative routing rule ('Use confirm_subscriber_by_email if you only have the address'). This is exactly the when/when-not/alternatives pattern.

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

All MailSenpai 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