Create group
mailerlite_create_groupDestructive
Creates a subscriber group/list (additive). MailerLite API: POST /groups.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the new group. |
mailerlite
by io.usefulapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says 'additive', but the annotation destructiveHint=true contradicts this. The description does not disclose other behavioral traits such as whether duplicate names are allowed, what happens on conflict, or auth requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence plus an API reference, which is concise and front-loaded. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite the simplicity of the tool (single parameter, no output schema), the description fails to clarify the contradiction with annotations and does not explain the response or uniqueness constraints. Incomplete for safe usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with one parameter. The description adds the endpoint info but no extra semantic beyond the schema's description of the 'name' parameter. The word 'additive' hints at behavior but not directly about the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Creates a subscriber group/list' which is a specific verb+resource, and distinguishes from siblings like list_groups. The API endpoint is also provided.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide explicit guidance on when to use this tool vs alternatives, but it's clear that it's for creating a group. No when-not-to-use or alternative suggestions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.8/5.0
Disambiguation5/5
Each tool targets a specific resource and action (e.g., subscriber, group, campaign) with no ambiguity. Even similar tools like list_subscribers and list_group_subscribers are clearly differentiated because one is global and the other is scoped to a group.
Naming Consistency5/5
All tools follow the consistent pattern 'mailerlite_verb_noun' (e.g., list_subscribers, create_group, get_campaign). The prefix ensures uniqueness, and verbs like list, get, create, upsert, assign are used uniformly.
Tool Count4/5
13 tools is reasonable for a MailerLite integration. It covers the core subscriber and group management well, while being lighter on other areas like campaigns and automations. The count is appropriate without being overwhelming.
Completeness3/5
The tool set covers subscriber and group management (CRUD for subscribers, create/list/assign groups) but is read-only for campaigns, automations, fields, segments, and webhooks. Missing operations like delete subscriber, delete/update group, and any write on campaigns indicate notable gaps.