Benchmark Email MCP integration for AI agents.
Connect AI agents to Benchmark Email through 4 structured actions, including get account summary, get contact details, and get contact list summary. Review a…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Benchmark Email integration exposes
The Benchmark Email Agent App exposes 4 provider-backed actions for marketing and communication work. Its current contract lets an authorized agent get the current benchmark email account summary and image storage plan details, get detailed information for a specific benchmark email contact email within a specific list, and get summary counts for a benchmark email contact list, including active, bounced, pending, and unsubscribed contacts. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Benchmark Email account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Benchmark Email capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_account_summaryREADGet the current Benchmark Email account summary and image storage plan details.
get_contact_detailsREADGet detailed information for a specific Benchmark Email contact email within a specific list.
INPUTS: list_id / email
get_contact_list_summaryREADGet summary counts for a Benchmark Email contact list, including active, bounced, pending, and unsubscribed contacts.
INPUTS: list_id
get_contacts_in_listREADGet paginated contacts from a Benchmark Email list with optional search, filter, and sorting parameters.
INPUTS: list_id / language / filter / order_by / sort_order
INPUT CONTRACTS
Know what the action needs before it runs.
get_contact_details
list_idREQUIRED- The contact list identifier that contains the contact.
emailREQUIRED- The email address of the contact to look up within the list.
get_contact_list_summary
list_idREQUIRED- The contact list identifier to summarize.
get_contacts_in_list
list_idREQUIRED- The contact list identifier to query.
languageOPTIONAL- The Benchmark Email language code forwarded to listGetFilteredContacts when needed.
filterOPTIONAL- The predefined contact subset filter returned by Benchmark Email.
order_byOPTIONAL- The contact field used for sorting list results.
sort_orderOPTIONAL- The sort direction used for contact list results.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account Summary
Get the current Benchmark Email account summary and image storage plan details. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_account_summaryVerify with Get Contact Details
Get detailed information for a specific Benchmark Email contact email within a specific list. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_contact_detailsSAFETY BOUNDARY
Operate Benchmark Email with explicit limits
- Authorize Benchmark Email with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Benchmark Email data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Benchmark Email rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Benchmark Email task completed successfully.
CONNECTION MODEL
API key
Benchmark Email API token used in XMLAPI query parameters (token/method/output=json). Create or view it from your Benchmark Email developer settings and API guide: https://www.benchmarkemail.com/features/api/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Benchmark Email.