The Mailerlite MCP connector routes your AI agent's tool calls to Mailerlite's own MCP server through Scalekit. Each user signs in to Mailerlite once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 92 tools.
- Tools
- 92
- What they doRead · write · destructive
- 41 · 32 · 1941 read32 write19 destructive
- Users sign in with
- OAuth
- OAuth app
- Scalekit's or your own
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the Mailerlite MCP connection
In AgentKit > Connections, create a Mailerlite MCP connection. The name you give it is the
connection_nameyour code passes. See Configure connections.Scalekit credentials are available for Mailerlite MCP server, so you don't need to register an OAuth app.
Authorize a user and make your first call
quickstart.mts import { ScalekitClient } from '@scalekit-sdk/node'import 'dotenv/config'import { createInterface } from 'node:readline/promises'const scalekit = new ScalekitClient(process.env.SCALEKIT_ENVIRONMENT_URL,process.env.SCALEKIT_CLIENT_ID,process.env.SCALEKIT_CLIENT_SECRET,)const actions = scalekit.actionsconst connector = 'mailerlitemcp'const identifier = 'user_123'// Generate an authorization link for the userconst { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })console.log('Authorize Mailerlite MCP:', link)const rl = createInterface({ input: process.stdin, output: process.stdout })await rl.question('Press Enter after authorizing...')rl.close()// Make your first callconst result = await actions.executeTool({connector,identifier,toolName: 'mailerlitemcp_get_auth_status',toolInput: { context: 'YOUR_CONTEXT' },})console.log(result)Terminal window npx tsx quickstart.mtsquickstart.py import osfrom scalekit import ScalekitClientfrom dotenv import load_dotenvload_dotenv()scalekit_client = ScalekitClient(env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),client_id=os.getenv("SCALEKIT_CLIENT_ID"),client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),)actions = scalekit_client.actionsconnection_name = "mailerlitemcp"identifier = "user_123"# Generate an authorization link for the userlink_response = actions.get_authorization_link(connection_name=connection_name,identifier=identifier,)print("Authorize Mailerlite MCP:", link_response.link)input("Press Enter after authorizing...")# Make your first callresult = actions.execute_tool(tool_input={"context":"YOUR_CONTEXT"},tool_name="mailerlitemcp_get_auth_status",connection_name=connection_name,identifier=identifier,)print(result)Terminal window python quickstart.pyEach user signs in once. See Authorize a user for the full flow and statuses.
Tools
Pass the exact name toexecute_toolmailerlitemcp_build_custom_automationValidate an automation plan before creating it.Read-onlyBuild Custom Automation
Validate an automation plan before creating it. Checks trigger type, steps, and optionally discovers matching resources.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
stepsarrayrequired- Planned automation steps in order
trigger_typestringrequired- The trigger type for the automationone of
subscriber_joins_groupform_completedabandoned_cartsubscriber_joins_segment resource_namestring- Optional resource name to search for (partial match)
resource_typestring- Resource type to look up. Defaults based on trigger: group for subscriber_joins_group, form for form_completed, shop for abandoned_cart, segment for subscriber_joins_segmentone of
groupformshopsegment
mailerlitemcp_discover_automation_templatesSearch and discover available automation templates by type and user intent.Read-onlyDiscover Automation Templates
Search and discover available automation templates by type and user intent.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
typestringrequired- Template type to retrieveone of
allwelcomepromotionremindereventfeedbackdate user_intentstring- The user's specific automation goal (e.g., welcome series, abandoned cart)
mailerlitemcp_dry_run_automationPreview an automation flow by sending a test run to a specified email address.Read-onlyDry Run Automation
Preview an automation flow by sending a test run to a specified email address.
Inputs
automation_idstringrequired- ID of automation to test
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
test_emailstringrequired- Email address for virtual test subscriber
mailerlitemcp_fetchFetch a MailerLite resource by its ID.Read-onlyFetch
Fetch a MailerLite resource by its ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
idstringrequired- Identifier returned from the search tool (e.g., "campaign:123", "group:456"), or a bare id when "type" is also given
typestring- Resource kind, required only when "id" has no "<kind>:" prefixone of
campaigngroupformautomationsegment
mailerlitemcp_get_auth_statusCheck the current authentication status and account details for the connected MailerLite account.Read-onlyGet Auth Status
Check the current authentication status and account details for the connected MailerLite account.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
mailerlitemcp_get_automation_activityRetrieve activity logs for an automation, filtered by date, status, or subscriber search.Read-onlyGet Automation Activity
Retrieve activity logs for an automation, filtered by date, status, or subscriber search.
Inputs
automation_idstringrequired- The ID of the automation
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
statusstringrequired- Filter by activity status
date_fromstring- Filter from date (Y-m-d). For completed/canceled/failed statuses
date_tostring- Filter to date (Y-m-d). For completed/canceled/failed statuses
limitinteger- Number of results per page (default 10)
pageinteger- Page number
scheduled_fromstring- Filter scheduled from date (Y-m-d). For active status
scheduled_tostring- Filter scheduled to date (Y-m-d). For active status
searchstring- Search by subscriber email
mailerlitemcp_get_automation_emailRead one email step of an automation: subject, preheader, sender, reply-to, plain text and HTML.Read-onlyGet Automation Email
Read one email step of an automation: subject, preheader, sender, reply-to, plain text and HTML. Works for emails designed in the visual editor and for HTML set via update_automation_email_content. The HTML is the stored source: merge tags such as {$name} and {$unsubscribe} and conditional blocks are kept as written, so edit it in place and pass it back to update_automation_email_content without re-adding them.
Inputs
automation_idstringrequired- Automation ID
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
step_indexintegerrequired- Email step index (0-based, only counts email steps, in the order the automation runs them), same as update_automation_email.
mailerlitemcp_get_automation_statsGet performance stats for an automation: sent, opens, clicks and unsubscribes, overall and for each email.Read-onlyGet Automation Stats
Get performance stats for an automation: sent, opens, clicks and unsubscribes, overall and for each email. list_automations already shows a short summary per automation. Use this tool for monthly totals, per-email numbers, or one email's numbers over a date range. Args: - automation_id (string): The automation ID. - months (3 | 6 | 12, optional): How many months of monthly totals to return. Defaults to 3. - email_id (string, optional): One email in the automation (an id from this tool's emails[]). Returns that email's engagement and deliverability instead of the automation overview. - start_date, end_date (Y-m-d, optional): Limit the email_id report to a period, both days included. Pass both or neither, and only with email_id. Returns: without email_id, { automation_id, activity, monthly[], emails[] }. activity counts subscriber runs by status. Each email in emails[] has id, name, subject and stats. With email_id, { automation_id, email_report: { email_id, engagement, deliverability } }.
Inputs
automation_idstringrequired- The ID of the automation
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
email_idstring- Return the report for this one email in the automation
end_datestring- Report end date (Y-m-d), included. Only with email_id, together with start_date
monthsstring- Months of monthly totals to return: 3, 6 or 12 (default 3)
start_datestring- Report start date (Y-m-d). Only with email_id, together with end_date
mailerlitemcp_get_campaignRetrieve details for a specific campaign by its campaign ID.Read-onlyGet Campaign
Retrieve details for a specific campaign by its campaign ID.
Inputs
campaign_idstringrequired- The ID of the campaign
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
mailerlitemcp_get_campaign_link_recipientsList subscribers who clicked a specific link in a campaign.Read-onlyGet Campaign Link Recipients
List subscribers who clicked a specific link in a campaign.
Inputs
campaign_idstringrequired- The ID of the campaign
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
link_idstringrequired- The ID of the link
limitstring- Number of results per page (10, 25, 50, or 100)
orderstring- Sort directionone of
ascdesc order_bystring- Sort fieldone of
idclicks_count pageinteger- Page number for pagination
searchstring- Search by subscriber email
mailerlitemcp_get_campaign_linksList all tracked links for a campaign.Read-onlyGet Campaign Links
List all tracked links for a campaign.
Inputs
campaign_idstringrequired- The ID of the campaign
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
mailerlitemcp_get_campaign_subscribersList subscribers for a campaign, filtered by activity type (opened, clicked, bounced, etc.).Read-onlyGet Campaign Subscribers
List subscribers for a campaign, filtered by activity type (opened, clicked, bounced, etc.).
Inputs
campaign_idstringrequired- The ID of the campaign
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
limitinteger- Number of results (allowed values: 10, 25, 50, 100)
pageinteger- Page number for pagination
searchstring- Search by subscriber email
sortstring- Sort fieldone of
idupdated_atclicks_countopens_count typestring- Filter by activity typeone of
openedunopenedclickedunsubscribedforwardedhardbouncedsoftbouncedjunk
mailerlitemcp_get_dashboard_linkGet a direct link to a MailerLite dashboard resource (automation or other context).Read-onlyGet Dashboard Link
Get a direct link to a MailerLite dashboard resource (automation or other context).
Inputs
resource_typestringrequired- What kind of dashboard link to buildone of
automationcampaignformsegmentgroupsettings_domainssettings_accountsettings_apisettings_billingsettings_securitysettings_profilesettings_teamsettings_webhookssettings_notificationssettings_integrationssettings_subscribesettings_unsubscribesettings_preference_centersettings_brand_styles contextstring- What the user needs to do (e.g., "design email", "review campaign")
resource_idstring- ID of the automation/campaign/form/segment/group. Not needed for any "settings_*" resource_type, or for "group" to get the groups list.
mailerlitemcp_get_ecommerce_reportGet e-commerce revenue reports: the orders and revenue attributed to campaigns and automations, and what a shop or subscriber has earned.Read-onlyGet Ecommerce Report
Get e-commerce revenue reports: the orders and revenue attributed to campaigns and automations, and what a shop or subscriber has earned. Read-only. Reports: - campaign: a campaign's order count, revenue, average order value and conversion rate in one shop, plus its best performing email. Requires campaign_id and shop_id. - campaign_orders: the individual orders attributed to a campaign. Requires campaign_id and shop_id. - shop: a shop's attributed orders and revenue over a period of up to one year, as totals and a day-by-day series. Requires shop_id, start_date and end_date. - subscriber: a subscriber's lifetime order count, revenue and average order value in one shop. Requires subscriber_id and shop_id. - subscriber_orders: a subscriber's orders in one shop. Requires subscriber_id and shop_id. - automation: an automation's attributed orders, revenue and conversion rate, plus its best performing email. Requires automation_id. - automation_email: one automation email's attributed orders and revenue. Requires automation_id and email_id. - automation_orders: the individual orders attributed to an automation. Requires automation_id. - settings: whether e-commerce tracking is on for campaigns and automations, and the attribution window in days. The automation reports cover the automation's whole history unless start_date and end_date are given, and shop_id narrows them to one shop. Revenue is attributed in the background within the attribution window, so a very recent order may not be counted yet.
Inputs
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
reportstringrequired- Report to return: campaign, campaign_orders, shop, subscriber, subscriber_orders, automation, automation_email, automation_orders, settingsone of
campaigncampaign_ordersshopsubscribersubscriber_ordersautomationautomation_emailautomation_orderssettings automation_idstring- Automation id, for the automation reports
campaign_idstring- Campaign id, for the campaign reports
email_idstring- Automation email id, for the automation_email report
end_datestring- Last day of the period (Y-m-d), included. Pass together with start_date
limitinteger- Page size for the *_orders reports (default 10)
pageinteger- Page number for the *_orders reports, starting from 1
shop_idstring- E-commerce shop id. Required for the campaign, shop and subscriber reports
start_datestring- First day of the period (Y-m-d), for the shop and automation reports
subscriber_idstring- Subscriber id, for the subscriber reports
mailerlitemcp_get_formRetrieve details for a specific signup form by its form ID.Read-onlyGet Form
Retrieve details for a specific signup form by its form ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
form_idstringrequired- The ID of the form
mailerlitemcp_get_form_subscribersList subscribers who signed up through a specific form.Read-onlyGet Form Subscribers
List subscribers who signed up through a specific form.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
form_idstringrequired- The ID of the form
filterstring- Filter subscribers
limitinteger- Number of subscribers to return (1-100)
pageinteger- Page number for pagination
mailerlitemcp_get_group_subscribersList subscribers in a specific group, with optional cursor-based pagination.Read-onlyGet Group Subscribers
List subscribers in a specific group, with optional cursor-based pagination.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
group_idstringrequired- The ID of the group
cursorstring- Cursor for pagination
limitinteger- Number of subscribers to return (1-100)
mailerlitemcp_get_more_toolsCheck for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.Read-onlyGet More Tools
Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.
Inputs
contextstringrequired- A description of your goal and what kind of tool would help accomplish it.
mailerlitemcp_get_segmentRetrieve details for a specific segment by its segment ID.Read-onlyGet Segment
Retrieve details for a specific segment by its segment ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
segment_idstringrequired- The ID of the segment
mailerlitemcp_get_segment_subscribersList subscribers matching a segment, with cursor pagination and status filtering.Read-onlyGet Segment Subscribers
List subscribers matching a segment, with cursor pagination and status filtering.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
segment_idstringrequired- The ID of the segment
cursorstring- Cursor for pagination
limitinteger- Number of subscribers to return (1-100)
statusstring- Filter by subscriber statusone of
activeunsubscribedunconfirmedbouncedjunk
mailerlitemcp_get_subscriberRetrieve a subscriber's full profile by their subscriber ID.Read-onlyGet Subscriber
Retrieve a subscriber's full profile by their subscriber ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
subscriber_idstringrequired- The ID or email of the subscriber
mailerlitemcp_get_subscriber_activityRetrieve recent activity events for a subscriber (opens, clicks, etc.).Read-onlyGet Subscriber Activity
Retrieve recent activity events for a subscriber (opens, clicks, etc.).
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
subscriber_idstringrequired- The ID or email of the subscriber
mailerlitemcp_get_subscriber_countGet the total count of subscribers in your MailerLite account.Read-onlyGet Subscriber Count
Get the total count of subscribers in your MailerLite account.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
statusstring- Filter the count to subscribers with this statusone of
activeunsubscribedunconfirmedbouncedjunk
mailerlitemcp_get_webhookRetrieve details for a specific webhook by its webhook ID.Read-onlyGet Webhook
Retrieve details for a specific webhook by its webhook ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
webhook_idstringrequired- The ID of the webhook
mailerlitemcp_list_automationsList all automations in the account, with optional filtering to enabled automations only.Read-onlyList Automations
List all automations in the account, with optional filtering to enabled automations only.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
enabled_onlyboolean- Only show enabled automations
limitinteger- Maximum number of automations to return per page (1-100, default 50)default
50 pageinteger- Page number for pagination (default 1)
mailerlitemcp_list_campaign_languagesList languages available for campaign localization, with their numeric IDs, for use as `language_id` on create_campaign or update_campaign.Read-onlyList Campaign Languages
List languages available for campaign localization, with their numeric IDs, for use as `language_id` on create_campaign or update_campaign.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
mailerlitemcp_list_campaignsList campaigns in the account, with filtering by status and type.Read-onlyList Campaigns
List campaigns in the account, with filtering by status and type.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
cursorstring- Cursor for pagination
limitinteger- Number of campaigns to return (1-100, default 25)
statusstring- Filter by campaign statusone of
draftreadysent typestring- Filter by campaign typeone of
regularabresendmultivariate
mailerlitemcp_list_email_templatesList available email templates with optional search and pagination.Read-onlyList Email Templates
List available email templates with optional search and pagination.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
limitnumber- Maximum number of templates to return (default: 10)default
10 searchstring- Search filter for template names
mailerlitemcp_list_fieldsList all custom subscriber fields with optional filtering and sorting.Read-onlyList Fields
List all custom subscriber fields with optional filtering and sorting.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
keywordstring- Filter by keyword
limitinteger- Number of fields to return
pageinteger- Page number
sortstring- Sort field
typestring- Filter by field typeone of
textnumberdate
mailerlitemcp_list_form_templatesList available form templates, filtered by form type.Read-onlyList Form Templates
List available form templates, filtered by form type.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
typestringrequired- Form template typeone of
popuppromotionembedded limitinteger- Number of templates to return (default: 25)
mailerlitemcp_list_formsList all signup forms with optional filtering by name, type, and sorting.Read-onlyList Forms
List all signup forms with optional filtering by name, type, and sorting.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
typestringrequired- The type of forms to listone of
popupembeddedpromotion limitinteger- Number of forms to return (1-100)
namestring- Filter by form name
pageinteger- Page number for pagination
sortstring- Sort field
mailerlitemcp_list_resourcesList MailerLite resources (groups, forms, segments, or shops) with optional name filtering.Read-onlyList Resources
List MailerLite resources (groups, forms, segments, or shops) with optional name filtering.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
resource_typestringrequired- Type of resource to list: group, form, shop, or segment (singular or plural)
name_filterstring- Optional filter by name (partial match)
mailerlitemcp_list_segmentsList all dynamic segments with pagination.Read-onlyList Segments
List all dynamic segments with pagination.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
limitinteger- Number of segments to return (1-100)
pageinteger- Page number for pagination
mailerlitemcp_list_subscribersList subscribers with cursor-based pagination, status filtering, and limit control.Read-onlyList Subscribers
List subscribers with cursor-based pagination, status filtering, and limit control.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
cursorstring- Cursor for pagination
limitinteger- Number of subscribers to return (1-100, default 25)
statusstring- Filter by subscriber statusone of
activeunsubscribedunconfirmedbouncedjunk
mailerlitemcp_list_timezonesList timezones and their numeric IDs, for use as `schedule.timezone_id` when scheduling a campaign.Read-onlyList Timezones
List timezones and their numeric IDs, for use as `schedule.timezone_id` when scheduling a campaign. Pass `search` (e.g. "Vilnius", "+02:00") to filter instead of listing all ~400 rows.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
searchstring- Case-insensitive substring match against the timezone name or offset
mailerlitemcp_list_webhooksList all configured webhooks in the account.Read-onlyList Webhooks
List all configured webhooks in the account.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
mailerlitemcp_searchSearch across MailerLite subscribers and groups by query string.Read-onlySearch
Search across MailerLite subscribers and groups by query string.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
querystringrequired- Text to search for across MailerLite resources
limitinteger- Maximum number of results to return (default 10)
mailerlitemcp_select_resourceSelect a specific MailerLite resource by ID and type for use in an automation workflow.Read-onlySelect Resource
Select a specific MailerLite resource by ID and type for use in an automation workflow.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
resource_idstringrequired- The ID of the selected resource
resource_namestringrequired- The name of the selected resource
resource_typestringrequired- The type of the selected resource (singular or plural)
mailerlitemcp_start_automation_conversationStart a guided conversation to help build an automation from a natural language request.Read-onlyStart Automation Conversation
Start a guided conversation to help build an automation from a natural language request.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
user_requeststringrequired- What the user asked for
mailerlitemcp_validate_email_contentValidate email content (subject and body) against MailerLite best practices.Read-onlyValidate Email Content
Validate email content (subject and body) against MailerLite best practices. Provide the subject and plain_text you have drafted, and this tool will check for issues like subject length, spam trigger words, missing call-to-action, and body length limits.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
plain_textstringrequired- The plain text email body to validate
subjectstringrequired- The email subject line to validate
mailerlitemcp_validate_subject_linesValidate a list of email subject line candidates against MailerLite best practices.Read-onlyValidate Subject Lines
Validate a list of email subject line candidates against MailerLite best practices. Provide subject lines you have drafted, and this tool will check each one for length, spam trigger words, and other issues.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
subject_linesarrayrequired- Array of subject line candidates to validate
mailerlitemcp_add_automation_stepAdd a new email or delay step to an EXISTING automation.WriteAdd Automation Step
Add a new email or delay step to an EXISTING automation. By default the step is appended at the end of the flow; pass after_step_id to insert it right after a specific step instead (get step ids from dry_run_automation). IMPORTANT: like create_automation, an email step's HTML content cannot be authored via the API — design it in the dashboard, or set the subject/content afterwards with update_automation_email / update_automation_email_content. The automation must be disabled to add steps.
Inputs
automation_idstringrequired- The ID of the automation
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
typestringrequired- Step typeone of
emaildelayconditionabtestaction actionstring- Action only: the action and its complete config
after_step_idstring- Insert the new step right after this step id. Omit to append at the end.
branchstring- Required when after_step_id is a condition step ("yes"/"no") or to target one path of an A/B test ("a_path"/"b_path"/"c_path").one of
yesnoa_pathb_pathc_path conditionsarray- Condition only: 1 to 5 conditions
delay_unitstring- Delay unit for a delay stepone of
minuteshoursdays delay_valuenumber- Delay duration for a delay step
email_subjectstring- Subject line for an email step
fromstring- Sender email for the email step. Must be verified on the MailerLite account.
from_namestring- Sender name for the email step
matching_typestring- Condition only: pass when any condition matches, or only when all do. Defaults to any.one of
anyall move_to_branchstring- If the chosen condition branch already holds a step, which branch that step moves to. For a new condition: which branch the steps below the insertion point move into. Defaults to yes.one of
yesno reply_tostring- Reply-to email for the email step. Must be verified. Defaults to the sender email.
split_percentagesarray- A/B split only: percentage per path, in path order A, B, C. Must sum to 100.
mailerlitemcp_add_subscriberAdd a new subscriber to your MailerLite account, optionally assigning them to groups and setting custom fields.WriteAdd Subscriber
Add a new subscriber to your MailerLite account, optionally assigning them to groups and setting custom fields.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
emailstringrequired- The email address of the subscriber
fieldsobject- Custom fields for the subscriber
groupsarray- Group IDs to add the subscriber to
namestring- The name of the subscriber
resubscribeboolean- Whether to resubscribe a previously unsubscribed subscriber
statusstring- Subscriber status (default: active)one of
activeunsubscribedunconfirmedbouncedjunk
mailerlitemcp_assign_subscriber_to_groupAdd an existing subscriber to a MailerLite group by subscriber ID and group ID.WriteAssign Subscriber To Group
Add an existing subscriber to a MailerLite group by subscriber ID and group ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
group_idstringrequired- The ID of the group
subscriber_idstringrequired- The ID or email of the subscriber
mailerlitemcp_batch_requestsExecute up to 50 MailerLite API requests in a single batch call.WriteBatch Requests
Execute up to 50 MailerLite API requests in a single batch call. Webhooks are not supported.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
requestsarrayrequired- Array of API requests to execute (max 50)
mailerlitemcp_cancel_campaignCancel a scheduled or delivering campaign by its campaign ID.WriteCancel Campaign
Cancel a scheduled or delivering campaign by its campaign ID.
Inputs
campaign_idstringrequired- The ID of the campaign to cancel
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
mailerlitemcp_copy_automation_stepDuplicate a step, with its configuration, and insert the copy into the workflow.WriteCopy Automation Step
Duplicate a step, with its configuration, and insert the copy into the workflow. By default the copy becomes the first step; pass parent_id to place it after a specific step instead. The automation must be disabled and under its step limit.
Inputs
automation_idstringrequired- The ID of the automation
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
step_idstringrequired- The step to copy
branchstring- Which branch of the parent to place the copy into, for a condition or A/B test parentone of
yesnoa_pathb_pathc_path move_to_branchstring- If the target branch already holds a step, which branch that step moves toone of
yesno parent_idstring- Place the copy after this step id. Omit to make it the first step.
mailerlitemcp_create_campaignCreate a new email campaign.WriteCreate Campaign
Create a new email campaign. The sender email must be a verified sender on your MailerLite account.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
fromstringrequired- The sender email address (must be verified on the MailerLite account)
from_namestringrequired- The sender name
namestringrequired- The name of the campaign
subjectstringrequired- The email subject line
typestringrequired- The type of campaignone of
regularabresendmultivariate contentstring- The HTML content of the email (optional - can be designed in dashboard)
groupsarray- Group IDs to send to. Cannot be combined with `segments`.
language_idstring- Language ID for the unsubscribe template, from list_campaign_languages. Defaults to the account language if omitted.
reply_tostring- Reply-to email address
segmentsarray- Segment IDs to send to. Cannot be combined with `groups`.
mailerlitemcp_create_fieldCreate a new custom subscriber field for storing additional subscriber data.WriteCreate Field
Create a new custom subscriber field for storing additional subscriber data.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
namestringrequired- The name of the field
typestringrequired- The type of the fieldone of
textnumberdate
mailerlitemcp_create_formCreate a new signup form (popup, embedded, or promotion) linked to one or more groups.WriteCreate Form
Create a new signup form (popup, embedded, or promotion) linked to one or more groups.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
groupsarrayrequired- Numeric group ID strings to assign new subscribers to (required, at least one) — obtained from list_resources with resource_type "group", not a group name
namestringrequired- The name of the form
typestringrequired- The type of form to createone of
popupembeddedpromotion
mailerlitemcp_create_groupCreate a new subscriber group to organize your mailing list.WriteCreate Group
Create a new subscriber group to organize your mailing list.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
namestringrequired- The name of the group
mailerlitemcp_create_segmentCreate a new dynamic segment based on subscriber filter conditions.WriteCreate Segment
Create a new dynamic segment based on subscriber filter conditions.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
namestringrequired- The name of the segment
filterarray- Filter rules: [[{"operator": "...", "args": [...]}]]. Inner arrays are AND groups, outer array is OR between groups. Do not wrap this in a {"rules": [...]} object. See the tool description for the valid operator/field reference. Omit to create a segment without filters.
mailerlitemcp_create_webhookCreate a webhook to receive real-time event notifications from MailerLite.WriteCreate Webhook
Create a webhook to receive real-time event notifications from MailerLite.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
eventsarrayrequired- Webhook events to subscribe to
urlstringrequired- The URL to send webhook payloads to
batchableboolean- Required as true for campaign.open, campaign.click, and subscriber.deleted events
enabledboolean- Whether the webhook is enabled
namestring- A name for the webhook
mailerlitemcp_import_subscribers_to_groupBulk-import multiple subscribers into a group in one request.WriteImport Subscribers To Group
Bulk-import multiple subscribers into a group in one request.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
group_idstringrequired- The ID of the group to import to
subscribersarrayrequired- Array of subscribers to import
autorespondersboolean- Whether to trigger autoresponders
resubscribeboolean- Whether to resubscribe previously unsubscribed subscribers
mailerlitemcp_manage_ecommerce_product_variantsSync, update or delete a product's variants, such as its sizes or colours.WriteManage Ecommerce Product Variants
Sync, update or delete a product's variants, such as its sizes or colours. Requires `shop_id` and `product_id` (the product's MailerLite ID). `sync` creates or updates variants from a list: a variant with a `resource_id` updates the existing variant with that id or is created, and one without is always added. When any variant in the list has a `resource_id`, the product's other variants that have a `resource_id` but are missing from the list are deleted. To read variants, use read_ecommerce_data with resource `product_variants`.
Inputs
actionstringrequired- Operation: sync, update, deleteone of
syncupdatedelete contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
product_idstringrequired- The product's MailerLite ID
shop_idstringrequired- Parent shop id
dataobject- Replacement variant for update. Fields: name (string, required, e.g. "Large / Blue"), attributes (object, required, e.g. {"size": "L"}), price_type (fixed | increment: replace or add to the product price), price (float, required with price_type), resource_id (string, your own id), image_url (string)
idstring- Variant id — required for update and delete
variantsarray- Variants for sync. Fields: name (string, required, e.g. "Large / Blue"), attributes (object, required, e.g. {"size": "L"}), price_type (fixed | increment: replace or add to the product price), price (float, required with price_type), resource_id (string, your own id), image_url (string)
mailerlitemcp_read_ecommerce_dataList or fetch MailerLite e-commerce data: shops, products, customers, orders, categories, carts, cart items, and the products in a category.WriteRead Ecommerce Data
List or fetch MailerLite e-commerce data: shops, products, customers, orders, categories, carts, cart items, and the products in a category. Read-only — it cannot create, change or delete anything; use the manage_ecommerce_* tools for that. `shop_id` is required for every resource except `shops`; `cart_items` also requires `cart_id`; `category_products` also requires `category_id` and supports only the `list` action. Use `action: "get"` with `id` to fetch one record, and the `list` cursor for further pages.
Inputs
actionstringrequired- Read to perform: list a collection, or get one record by `id`one of
listget contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
resourcestringrequired- E-commerce resource to read: shops, products, product_variants, customers, orders, categories, carts, cart_items, category_productsone of
shopsproductsproduct_variantscustomersorderscategoriescartscart_itemscategory_products cart_idstring- Parent cart id — required for `cart_items`
category_idstring- Parent category id — required for `category_products`
filterobject- Filters for list, sent as filter[key]=value. products: name (contains), type (one-time | subscription | booking), enabled (true | false), category (category id), exclude_from_automations (true | false). customers: email (exact match). orders: status (pending | complete), customer (customer id), attributed (true | false), email_id (orders attributed to this email), and on the MailerLite shop only from and to (Y-m-d), name, currency. categories: exclude_from_automations.
idstring- Resource id — required for the get action
limitinteger- Page size for list (1-100)
pageinteger- Page number for list, starting from 1
product_idstring- Parent product id (MailerLite ID) — required for `product_variants`
shop_idstring- Parent shop id — required for every resource except `shops`
sortstring- Sort field for list; prefix with - for descending. products: id, name, created_at. customers: id, email, created_at. orders: id, created_at.
mailerlitemcp_reorder_automation_stepMove a step — and everything below it — to a new position in an automation's workflow.WriteReorder Automation Step
Move a step — and everything below it — to a new position in an automation's workflow. Pass new_parent_step_id to place it after another step, or omit it to make it the first step. The automation must be disabled.
Inputs
automation_idstringrequired- The ID of the automation
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
dragged_step_idstringrequired- The single step to move. Its own children stay behind at the old position — use step_ids to move a sequence together instead.
branchstring- Which branch of the new parent to move into, for a condition or A/B test parentone of
yesnoa_pathb_pathc_path branch_for_childstring- If the target branch already holds a step, which branch that step moves toone of
yesno new_parent_step_idstring- Place the moved step(s) after this step id. Omit to make them the first step(s).
step_idsarray- An ordered list of step ids to move together as one group, in the order they should end up in after new_parent_step_id. Use this instead of dragged_step_id to move more than one step at once.
mailerlitemcp_replace_automation_triggerChange an automation trigger's TYPE (e.g.WriteReplace Automation Trigger
Change an automation trigger's TYPE (e.g. from subscriber_joins_group to subscriber_joins_segment). This clears the trigger's configuration — follow up with update_automation_trigger to set the new type's data. The automation must be disabled to edit its trigger.
Inputs
automation_idstringrequired- The ID of the automation
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
typestringrequired- The new trigger typeone of
subscriber_joins_groupform_completedabandoned_cartsubscriber_joins_segmentfield_updatedanniversaryclicks_link trigger_idstring- Trigger ID to replace. Omit when the automation has only one trigger.
mailerlitemcp_schedule_campaignSchedule a campaign for immediate or future delivery.WriteSchedule Campaign
Schedule a campaign for immediate or future delivery. Use delivery 'instant' to send now.
Inputs
campaign_idstringrequired- The ID of the campaign to schedule
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
deliverystringrequired- Delivery type: "instant" sends now, "scheduled" sends at a specific time, "timezone_based" sends per subscriber timezone, "smart_sending" uses AI-optimized send timesone of
instantscheduledtimezone_basedsmart_sending scheduleobject- Schedule details — required when delivery is "scheduled" or "timezone_based"
mailerlitemcp_send_test_automationSend a test run of an automation to a specified email address.WriteSend Test Automation
Send a test run of an automation to a specified email address.
- Idempotent
Inputs
automation_idstringrequired- ID of automation to test
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
emailstringrequired- Your email address to receive the test emails
mailerlitemcp_unassign_subscriber_from_groupRemove a subscriber from a group by subscriber ID and group ID.WriteUnassign Subscriber From Group
Remove a subscriber from a group by subscriber ID and group ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
group_idstringrequired- The ID of the group
subscriber_idstringrequired- The ID or email of the subscriber
mailerlitemcp_update_automationRename an existing automation.WriteUpdate Automation
Rename an existing automation. Only changes the name shown in the automations list — the trigger and steps are untouched. Works whether the automation is active or disabled. Use update_automation_trigger to change what starts it, or add_automation_step to add steps.
Inputs
automation_idstringrequired- The ID of the automation
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
namestringrequired- New name for the automation
enabledboolean- true to activate (sends to subscribers), false to deactivate
reentryobject- Re-entry settings
mailerlitemcp_update_automation_delayUpdate the delay duration and unit for a specific step in an automation.WriteUpdate Automation Delay
Update the delay duration and unit for a specific step in an automation.
- Idempotent
Inputs
automation_idstringrequired- Automation ID
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
step_indexnumberrequired- Delay step index (0-based, only counts delay steps, in the order the automation runs them).
unitstringrequired- Delay duration unitone of
minuteshoursdays valuenumberrequired- Delay duration value (must be positive)
mailerlitemcp_update_automation_emailUpdate the subject and plain text content for an email step in an automation.WriteUpdate Automation Email
Update the subject and plain text content for an email step in an automation.
- Idempotent
Inputs
automation_idstringrequired- Automation ID
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
step_indexnumberrequired- Email step index (0-based, only counts email steps, in the order the automation runs them). Index 0 is the first email `dry_run_automation` reports, not the first email in the raw API step array.
subjectstringrequired- Email subject line. Omit to keep the current one.
fromstring- Sender email for the email step. Must be verified on the MailerLite account.
from_namestring- Sender name for the email step
plain_textstring- Plain text email content
preheaderstring- Preview text shown after the subject in the inbox. Omit to keep the current one. Personalize with {$name}. {{ }}, links and code are not allowed.
reply_tostring- Reply-to email for the email step. Must be verified. Defaults to the sender email.
mailerlitemcp_update_automation_email_contentReplace the HTML body of an automation email.WriteUpdate Automation Email Content
Replace the HTML body of an automation email. This overwrites the existing email design — any content previously created in the dashboard editor is lost. Use update_automation_email to change the subject or plain text instead.
Inputs
automation_idstringrequired- Automation ID
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
htmlstringrequired- Full HTML body to set as the email content
email_idstring- ID of the email record attached to the step. This is step.email_id, NOT the step id. Prefer step_index - a step update can replace the underlying email record, and writing to a replaced id succeeds against a record nothing points at. Ignored when step_index is given.
step_indexinteger- Email step index (0-based, only counts email steps, in the order the automation runs them), same as update_automation_email. Preferred over email_id: it is resolved to the step current email when the call runs, so it cannot go stale.
mailerlitemcp_update_automation_triggerUpdate the configuration of an automation's existing trigger — for example the group_ids for subscriber_joins_group, or the segment_id for subscriber_joins_segment.WriteUpdate Automation Trigger
Update the configuration of an automation's existing trigger — for example the group_ids for subscriber_joins_group, or the segment_id for subscriber_joins_segment. Send the COMPLETE config in `data`: fields you leave out are cleared, not kept. This cannot change the trigger's TYPE — use replace_automation_trigger for that. The automation must be disabled to edit its trigger. Args: - automation_id (string): The automation to update. - trigger_id (string, optional): Omit it when the automation has exactly one trigger (the common case) — it resolves automatically. - data (object): Complete trigger configuration for the trigger's type, e.g. { group_ids: [...], exclude_group_ids: [] } for subscriber_joins_group, or { segment_id: "..." } for subscriber_joins_segment.
Inputs
automation_idstringrequired- The ID of the automation
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
dataobjectrequired- Complete trigger configuration for the trigger type. Omitted fields are cleared.
trigger_idstring- Trigger ID to update. Omit when the automation has only one trigger.
mailerlitemcp_update_campaignUpdate the name, subject, sender, or content of an existing campaign.WriteUpdate Campaign
Update the name, subject, sender, or content of an existing campaign.
Inputs
campaign_idstringrequired- The ID of the campaign to update
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
contentstring- New HTML content
fromstring- New sender email
from_namestring- New sender name
groupsarray- New group IDs to send to (replaces existing recipients). Cannot be combined with `segments`.
language_idstring- New language ID for the unsubscribe template, from list_campaign_languages. Omit to keep the campaign's current language unchanged.
namestring- New campaign name. Omit to keep the campaign's current name unchanged.
segmentsarray- New segment IDs to send to (replaces existing recipients). Cannot be combined with `groups`.
subjectstring- New email subject
mailerlitemcp_update_fieldRename a custom subscriber field.WriteUpdate Field
Rename a custom subscriber field.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
field_idstringrequired- The ID of the field to update
namestringrequired- The new name for the field
mailerlitemcp_update_formUpdate the name of an existing signup form.WriteUpdate Form
Update the name of an existing signup form.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
form_idstringrequired- The ID of the form to update
namestring- New name for the form
mailerlitemcp_update_groupRename an existing subscriber group.WriteUpdate Group
Rename an existing subscriber group.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
group_idstringrequired- The ID of the group to update
namestringrequired- The new name for the group
mailerlitemcp_update_segmentUpdate the name of an existing segment.WriteUpdate Segment
Update the name of an existing segment.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
namestringrequired- New name for the segment
segment_idstringrequired- The ID of the segment to update
mailerlitemcp_update_subscriberUpdate an existing subscriber's name, status, or custom fields.WriteUpdate Subscriber
Update an existing subscriber's name, status, or custom fields.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
subscriber_idstringrequired- The ID or email of the subscriber
fieldsobject- Custom fields to update
namestring- The new name for the subscriber
mailerlitemcp_update_webhookUpdate the configuration of an existing webhook.WriteUpdate Webhook
Update the configuration of an existing webhook.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
webhook_idstringrequired- The ID of the webhook to update
batchableboolean- Required as true for campaign.open, campaign.click, and subscriber.deleted events
enabledboolean- Whether the webhook is enabled
eventsarray- Webhook events to subscribe to
namestring- A name for the webhook
urlstring- The URL to send webhook payloads to
mailerlitemcp_create_automationCreate a new automation workflow with a trigger type, trigger config, and ordered steps (email or delay).DestructiveCreate Automation
Create a new automation workflow with a trigger type, trigger config, and ordered steps (email or delay).
Inputs
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
namestringrequired- Name for the automation
stepsarrayrequired- Steps in order (email or delay)
trigger_configobjectrequired- Trigger configuration — the fields used depend on trigger_type (see the tool description)
trigger_typestringrequired- Trigger typeone of
subscriber_joins_groupform_completedabandoned_cartsubscriber_joins_segmentfield_updatedanniversaryclicks_link fromstring- Sender email for the email step. Must be verified on the MailerLite account.
from_namestring- Sender name for the email step
reply_tostring- Reply-to email for the email step. Must be verified. Defaults to the sender email.
mailerlitemcp_delete_automationPermanently delete an automation workflow by its automation ID.DestructiveDelete Automation
Permanently delete an automation workflow by its automation ID.
Inputs
automation_idstringrequired- The ID of the automation to delete
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
mailerlitemcp_delete_automation_stepDelete a step from an automation's workflow.DestructiveDelete Automation Step
Delete a step from an automation's workflow. For condition or A/B test steps, branch_to_delete says what happens to the branches below it: "all" removes every branch, or "yes"/"no"/"a_path"/"b_path"/"c_path" keeps that one branch and reattaches it in the step's place. A step that another step depends on — the target of a "go to step" action, of a condition, or of a delay's "continue from chosen step" — cannot be deleted until that reference is removed. The automation must be disabled.
Inputs
automation_idstringrequired- The ID of the automation
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
step_idstringrequired- The ID of the step to delete (from dry_run_automation)
branch_to_deletestring- Deprecated, use branch_to_keep. Despite the name it also names the branch to KEEP.
branch_to_keepstring- Required for condition/A/B test steps: the branch to keep, or "all" to remove every branch
mailerlitemcp_delete_campaignPermanently delete a campaign by its campaign ID.DestructiveDelete Campaign
Permanently delete a campaign by its campaign ID.
Inputs
campaign_idstringrequired- The ID of the campaign to delete
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
mailerlitemcp_delete_fieldDelete a custom subscriber field by its field ID.DestructiveDelete Field
Delete a custom subscriber field by its field ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
field_idstringrequired- The ID of the field to delete
mailerlitemcp_delete_formDelete a signup form by its form ID.DestructiveDelete Form
Delete a signup form by its form ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
form_idstringrequired- The ID of the form to delete
mailerlitemcp_delete_groupDelete a subscriber group by its group ID.DestructiveDelete Group
Delete a subscriber group by its group ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
group_idstringrequired- The ID of the group to delete
mailerlitemcp_delete_segmentDelete a dynamic segment by its segment ID.DestructiveDelete Segment
Delete a dynamic segment by its segment ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
segment_idstringrequired- The ID of the segment to delete
mailerlitemcp_delete_subscriberPermanently delete a subscriber by their subscriber ID.DestructiveDelete Subscriber
Permanently delete a subscriber by their subscriber ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
subscriber_idstringrequired- The ID or email of the subscriber to delete
mailerlitemcp_delete_webhookDelete a webhook by its webhook ID.DestructiveDelete Webhook
Delete a webhook by its webhook ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
webhook_idstringrequired- The ID of the webhook to delete
mailerlitemcp_install_templateInstall a MailerLite email template into your account by template ID.DestructiveInstall Template
Install a MailerLite email template into your account by template ID.
Inputs
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
template_idstringrequired- ID of template to install
mailerlitemcp_manage_ecommerce_cart_itemsList, fetch, create, update or delete the line items of a cart.DestructiveManage E-commerce Cart Items
List, fetch, create, update or delete the line items of a cart. Requires `shop_id` and `cart_id`.
Inputs
actionstringrequired- Operation to perform: create, update, deleteone of
createupdatedelete cart_idstringrequired- Parent cart id (required for all actions)
contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
shop_idstringrequired- Parent shop id (required for all actions)
datastring- Request body. Fields: ecommerce_product_id (integer, required), ecommerce_product_variant_id (integer, a variant of that product), variant (string, free text), quantity (integer, default 1), price (float), resource_id (string)
idstring- Resource id — required for every action except create and import
mailerlitemcp_manage_ecommerce_cartsList, fetch or update shopping carts within a shop (carts cannot be created or deleted via the API).DestructiveManage E-commerce Carts
List, fetch or update shopping carts within a shop (carts cannot be created or deleted via the API). Requires `shop_id`.
Inputs
actionstringrequired- Operation to perform: updateone of
update contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
shop_idstringrequired- Parent shop id (required for all actions)
datastring- Request body. Fields: checkout_url (string), cart_total (float), ecommerce_customer_id (integer), resource_id (string)
idstring- Resource id — required for every action except create and import
mailerlitemcp_manage_ecommerce_categoriesList, fetch, create, update, delete or bulk-import product categories within a shop.DestructiveManage E-commerce Categories
List, fetch, create, update, delete or bulk-import product categories within a shop. Requires `shop_id`.
Inputs
actionstringrequired- Operation to perform: create, update, delete, importone of
createupdatedeleteimport contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
shop_idstringrequired- Parent shop id (required for all actions)
datastring- Request body. Fields: name (string, required), exclude_from_automations (boolean), resource_id (string). import: an array of category objects with the same fields.
idstring- Resource id — required for every action except create and import
mailerlitemcp_manage_ecommerce_category_productsList the products in a category, or attach/detach a product to/from a category.DestructiveManage E-commerce Category Products
List the products in a category, or attach/detach a product to/from a category. Requires `shop_id` and `category_id`; attach/detach also require `product_id`.
Inputs
actionstringrequired- Operation: attach, detachone of
attachdetach category_idstringrequired- Category id
contextstringrequired- Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
product_idstringrequired- Product id to attach or detach
shop_idstringrequired- Parent shop id
mailerlitemcp_manage_ecommerce_customersList, fetch, create, update or delete customers within a shop.DestructiveManage E-commerce Customers
List, fetch, create, update or delete customers within a shop. Requires `shop_id`.
Inputs
actionstringrequired- Operation to perform: create, update, delete, importone of
createupdatedeleteimport contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
shop_idstringrequired- Parent shop id (required for all actions)
datastring- Request body. Fields: email (string, required), name (string), last_name (string), accepts_marketing (boolean), total_spent (float), orders_count (integer), create_subscriber (boolean), resource_id (string), subscriber_fields (object keyed by field name). import: an array of customer objects with the same fields.
idstring- Resource id — required for every action except create and import
mailerlitemcp_manage_ecommerce_ordersList, fetch, create, update, delete or bulk-import orders within a shop.DestructiveManage E-commerce Orders
List, fetch, create, update, delete or bulk-import orders within a shop. Requires `shop_id`.
Inputs
actionstringrequired- Operation to perform: create, update, delete, importone of
createupdatedeleteimport contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
shop_idstringrequired- Parent shop id (required for all actions)
datastring- Request body. Fields: customer (object, required on create: email, name, last_name, accepts_marketing, create_subscriber), cart (object, required on create: items (array of ecommerce_product_id, ecommerce_product_variant_id, variant, quantity, price), checkout_url, cart_total), status (pending | complete), total_price (float), resource_id (string), created_at (date-time), without_automations (boolean). Update accepts status, total_price, without_automations. import: { orders: [order objects] }.
idstring- Resource id — required for every action except create and import
mailerlitemcp_manage_ecommerce_productsList, fetch, create, update, delete or bulk-import products within a shop.DestructiveManage E-commerce Products
List, fetch, create, update, delete or bulk-import products within a shop. Requires `shop_id`.
Inputs
actionstringrequired- Operation to perform: create, update, delete, import, change_status, assign_categoriesone of
createupdatedeleteimportchange_statusassign_categories contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
shop_idstringrequired- Parent shop id (required for all actions)
datastring- Request body. Fields: create/update: name (string, required), price (float), url (string), image (string, image url), short_description (string, max 255), description (string), exclude_from_automations (boolean), enabled (boolean), type (one-time | subscription | booking), categories (array of category ids), variants (array; name (string, required, e.g. "Large / Blue"), attributes (object, required, e.g. {"size": "L"}), price_type (fixed | increment: replace or add to the product price), price (float, required with price_type), resource_id (string, your own id), image_url (string)), resource_id (string). import: an array of product objects with the same fields, where categories are category names and are created if missing. change_status: status (boolean, true enables). assign_categories: categories (array of category ids, max 100), replace (boolean, also remove categories not in the list).
idstring- Resource id — required for every action except create and import
mailerlitemcp_manage_ecommerce_shopsList, fetch, create, update or delete MailerLite e-commerce shops.DestructiveManage E-commerce Shops
List, fetch, create, update or delete MailerLite e-commerce shops. Use `id` as the shop id for get/update/delete.
Inputs
actionstringrequired- Operation to perform: create, update, deleteone of
createupdatedelete contextstringrequired- Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
datastring- Request body. Fields: name (string, required), url (string, required), currency (string, required, ISO 4217 e.g. EUR), platform (string), group_id (integer), enable_popups (boolean), enabled (boolean), access_data (string)
idstring- Resource id — required for every action except create and import
No tools match.
