Skip to main content
Glama

Add Email List Members

add_email_list_members
Destructive

[publish] Adds addresses to a saved list (email_list_id or email_list_uuid), at most 10000 per call: items (each an address or {"email": "ali@x.com", "vars": {"name": "Ali"}}), or source="customers" (the customers that have an e-mail). Addresses already on the list and invalid ones are counted, not added.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_email_list_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNo
sourceNo
email_list_idNo
email_list_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag this as non-readonly, non-idempotent, destructive, and open-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a 10000-item batch cap and the key detail that duplicate and invalid addresses are counted rather than added, which tells the agent the call will not hard-fail on bad input. It does not describe the response shape or what happens on partial failure.

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?

One dense paragraph, front-loaded with the action and the target, then the size limit, then the two payload forms, then the dedup caveat. Every clause carries information an agent needs; nothing is padding.

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

Completeness4/5

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

For a four-parameter mutation with no output schema and no schema descriptions, the description covers the essentials: which list, what to add, how much per call, and how duplicates are treated. The remaining gaps are whether an identifier is mandatory and what the call returns, which matter but are secondary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the full burden and largely does so: it defines `items` as either bare addresses or objects of the form {"email": ..., "vars": {...}}, and explains `source="customers"` as an alternative population source. It names `email_list_id` and `email_list_uuid` as the target-list identifiers, though it never states that one of them is effectively required or that items and source are exclusive.

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?

States a specific verb and resource (adds addresses to a saved email list) and immediately scopes it with the identifier options. It is clearly distinguishable from siblings like remove_email_list_members, list_email_list_members, and edit_email_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explains the two mutually alternative input modes: explicit `items` payloads or `source="customers"` for existing customers with an email. It also gives a concrete volume ceiling of 10000 per call. It stops short of naming siblings such as import_email_campaign_recipients or stating when to prefer those instead.

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.