Skip to main content
Glama
thenavidm

Flodesk MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List all subscribers.

list_subscribers
Read-onlyIdempotent

Retrieve all subscribers, optionally filtered by status or segment, with pagination controls for managing email audiences and campaigns.

Instructions

List all subscribers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoThe page number. Defaults to 1.
statusNoOptional. The subscriber's status. `active`: The subscriber is currently active to receive marketing emails. `unsubscribed`: The subscriber has opted out of marketing emails. `unconfirmed`: The subscriber is pending for double opt-in confirmation. `bounced`: The subscriber's address is undeliverable due to a hard bounce. `complained`: The subscriber marked an email as spam. `cleaned`: The subscriber was cleaned, learn more [here](https://help.flodesk.com/en/articles/4747969#how_can_i_find_out_which_email_addresses_have_been_cleaned). `archived`: The subscriber was archived.
accountNoExact configured private account profile label; not a tenant or provider account ID.
per_pageNoThe number of records to be returned on each page. Defaults to 20. Maximum 100.
segment_idNoOptional. The segment's id. When included, returns only subscribers who were added to the given segment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • removedInput schema / properties / page / maximum
      Removed value: -9007199254740991
  2. First observedv2.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered without the description. The description adds nothing beyond that — no pagination behavior, no note on whether filtered lists are returned, no account-scoping semantics.

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

Conciseness3/5

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

It is a single short sentence with no padding, which is structurally clean. But the sentence merely echoes the title and therefore does not earn its place as a distinct piece of content — brevity here reflects under-specification, not disciplined concision.

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

Completeness2/5

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

A five-parameter, filterable list tool with no output schema needs the description to convey filtering and pagination behavior, and it conveys none of it. Saying "all subscribers" is actively incomplete given that status and segment_id exist to narrow the result set.

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 the five parameters (page, per_page, status with a full enum, account, segment_id) are already fully documented in the schema and the baseline is 3. The description contributes no additional parameter meaning, so it does not exceed the baseline.

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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent cannot tell from this text when to call list_subscribers versus get_subscriber or list_segments. The phrase "all subscribers" even obscures that status/segment filtering exists.

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