Skip to main content
Glama

Moosend MCP by usefulapi

Add or update a subscriber

moosend_add_subscriber
Destructive

WRITE: add one subscriber to a mailing list. If the email already exists in the list, that subscriber is UPDATED instead (and custom fields you omit are cleared). A previously unsubscribed address is re-subscribed. Rate limit 10 calls / 10 s. Moosend: POST /subscribers/{MailingListID}/subscribe.json.

Input Schema

NameRequiredDescriptionDefault
nameNoSubscriber name.
tagsNoSubscriber tags.
emailYesSubscriber email address.
preferencesNoPreference option values chosen by the subscriber (must match the list's preference options).
custom_fieldsNoCustom field values by field name, e.g. {"City":"Athens","Age":25}. Sent to Moosend as "Name=Value" pairs. WARNING: on an existing subscriber, any custom field NOT included is cleared — include every field you want to keep.
mailing_list_idYesMailing list ID (a GUID, from moosend_list_mailing_lists).
has_external_double_opt_inNoTrue if the subscriber already gave consent by other means.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond destructiveHint=true, the description discloses the critical behaviors: existing emails are UPDATED, omitted custom fields are cleared, unsubscribed addresses are re-subscribed, and there is a 10/10s rate limit. The destructive annotation is consistent with the disclosed clearing behavior rather than contradicted.

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?

Front-loaded with the 'WRITE:' marker and built from short, information-dense sentences. Every clause (upsert, field clearing, re-subscribe, rate limit, endpoint) carries distinct value with no padding.

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?

For a mutation tool with no output schema, the description covers the write semantics, side effects, rate limit, and endpoint mapping needed to call it correctly. Nothing essential 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 every parameter is already documented in the schema, including the custom_fields clearing warning. The description reinforces this but adds no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 ('add one subscriber to a mailing list') and then discloses the upsert behavior that defines this tool. An agent can distinguish it from moosend_update_subscriber because the description explains the add-or-update-on-conflict semantics that is intrinsic to this endpoint.

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

Usage Guidelines3/5

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

Usage is clearly implied by the upsert framing, but there is no explicit routing against the sibling moosend_update_subscriber or a statement of when-not to use this tool. The context is helpful yet leaves the add-vs-update-tool choice to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.