Skip to main content
Glama
thenavidm

Flodesk MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create or update a subscriber.

create_or_update_subscriber
Destructive

Add or update a Flodesk subscriber by email or ID, setting names, segments, custom fields, and opt-in preferences.

Instructions

Create or update a subscriber.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe subscriber's `id`. Either `email` or `id` must be included.
emailNoThe subscriber's `email`. Either `email` or `id` must be included.
accountNoExact configured private account profile label; not a tenant or provider account ID.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete native JSON body; do not mix with body flags or payload_file. Arrays use repeated JSON object flags or a whole native array in a private file.
optin_ipNoIP address from which the subscriber confirmed their opt-in.
last_nameNoThe subscriber's last name.
first_nameNoThe subscriber's first name.
segment_idsNoThe segments this subscriber will be added to. Cap at `50`.
double_optinNo
payload_fileNoAbsolute regular non-symlink JSON body file, at most 1 MiB. Cannot mix with payload/body flags.
custom_fieldsNoAn object containing custom field data. E.g. ``` "favorite_color": "Lavender" ```.
optin_timestampNoThe date and time the subscribers confirmed their opt-in in ISO 8601 format. E.g. `2023-01-02T15:04:05.999Z`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv3.0.0
    • addedInput schema / $defs
      Added value: +{
+  "double_optin": {
+    "description": "Whether or not to require the subscriber to confirm subscription via email.\n\nThis option is only available to set with new subscriber creation. Default to `false` if not indicated.",
+    "type": "boolean"
+  }
+}
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for the requested mutation or exclusive private output file."New value: +"Set true only when the user asked for exactly this action."
    • addedInput schema / properties / double_optin / $ref
      Added value: +"#/$defs/double_optin"
    • removedInput schema / properties / double_optin / description
      Removed value: -"Whether or not to require the subscriber to confirm subscription via email.\n\nThis option is only available to set with new subscriber creation. Default to `false` if not indicated."
    • removedInput schema / properties / double_optin / type
      Removed value: -"boolean"
    • addedInput schema / properties / payload / properties / double_optin / $ref
      Added value: +"#/$defs/double_optin"
    • removedInput schema / properties / payload / properties / double_optin / description
      Removed value: -"Whether or not to require the subscriber to confirm subscription via email.\n\nThis option is only available to set with new subscriber creation. Default to `false` if not indicated."
    • removedInput schema / properties / payload / properties / double_optin / type
      Removed value: -"boolean"
  2. First observedv2.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — it does not explain upsert resolution (which fields update vs create), merge vs overwrite behavior, or the meaning of the confirm flag. With annotations carrying the burden, a low 2 is fair for a description that contributes zero behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short but that brevity is under-specification rather than conciseness — a single sentence that duplicates the title and earns no place. There is no front-loading of substance because there is no substance.

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

Completeness1/5

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

For a 13-parameter mutation tool with nested objects, a payload-or-flags exclusivity model, no output schema, and destructive/idempotent annotations, this one-line restatement is wholly inadequate. Nothing about upsert semantics, the confirm gate, or account scoping is addressed.

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 92%, so the schema already documents nearly all 13 parameters, including the payload/payload_file exclusivity rules and the double_optin constraint. Baseline 3 applies; the description adds no parameter meaning whatsoever.

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

Purpose2/5

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

Tautological: description restates name/title.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no named alternatives. An agent cannot tell from this text whether to call this versus batch_create_or_update_subscribers or add_subscriber_to_segments, nor when an update path vs a create path is taken.

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

Deploy Server

Other Tools