mailerlite_list_groupsList subscriber groups/lists, optionally filtered by name. Page-paginated. MailerLite API: GET /groups.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Filter by name (→ filter[name]). | |
| page | No | Page number (page-based pagination). | |
| sort | No | Sort field, e.g. name, total, -total, created_at. | |
| limit | No | Max groups per page (default 25). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the read-only behavior is established. The description adds key behavioral details: page-based pagination and the API endpoint (GET /groups), which goes beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single concise sentence covering purpose, filtering, pagination, and API reference. No redundancy or unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with no output schema, the description covers essential aspects: what it lists, optional filtering, and pagination. The API reference adds useful context. Could mention return values (group objects) but not critical.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the description mentions filtering by name and pagination, which provides context. However, the description does little beyond echoing schema comments; the param details are already clear from the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'List subscriber groups/lists, optionally filtered by name. Page-paginated.' which clearly identifies the verb and resource. The sibling tools (e.g., mailerlite_create_group, mailerlite_list_group_subscribers) are distinct, so no confusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Describes optional filtering and pagination, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., mailerlite_list_group_subscribers for a specific group's members). No 'when not to use' or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.