mailerlite_list_fieldsList custom/default subscriber fields, optionally filtered by type or keyword. Page-paginated. MailerLite API: GET /fields.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (page-based pagination). | |
| type | No | Filter by field type (→ filter[type]): text | number | date. | |
| limit | No | Max fields per page (default 25). | |
| keyword | No | Filter by keyword (→ filter[keyword]). |
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 provide readOnlyHint=true, confirming safety. The description adds that it is page-paginated and uses a specific API endpoint. However, it does not disclose details like rate limits, data scope (e.g., all fields vs. subscriber-specific), or behavior when no filters are applied.
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?
The description is two sentences with no redundancy. It front-loads the main action and resource, then adds key details (filtering, pagination, API). Efficient and well-structured.
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 the main aspects: resource, filtering, and pagination. It could mention the probable return format (array of field objects), but given low complexity, it is mostly complete.
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%, so the schema already explains each parameter. The description restates that filtering by type or keyword is possible but adds no new semantic meaning beyond what the schema provides.
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 custom/default subscriber fields' with a specific verb and resource, and it mentions optional filtering and pagination. This clearly distinguishes it from sibling tools that deal with subscribers, groups, campaigns, etc.
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?
The description lacks explicit guidance on when to use this tool vs. alternatives like mailerlite_list_subscribers. It does not mention prerequisites, exclusions, or context for choosing this tool over others.
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.