Inspect active email-list summaries and subscriber counts through Moosend v3 using your account API key. Read one explicit page or one known list. These commands exclude subscriber addresses, creator/updater IPs, custom fields, imports and preferences, and do not change lists, trigger automations, send campaigns or provide managed OAuth.
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List Moosend mailing lists — moosend.lists.list |
Read |
Read a Moosend mailing-list summary — moosend.lists.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Moosend, then enter the issued values in the connection form below.
- Create or sign in to your Moosend account. Open Settings → API Key and choose Copy, or Generate API key if you need a new one. Enter it in Moosend API key in this connection; it is not your login password. This account-wide credential can permit writes, but these commands only inspect list summaries and subscriber counts. Select lists.list or lists.get, save and create an Tooluse.net API key scoped to the selected reads. Start with Page 1 and PageSize 10; use a returned ID as MailingListID for lists.get or advance Page explicitly. Regenerate/replace the provider key from its settings and update this connection when rotating. The supported base is api.moosend.com/v3; no managed OAuth or automatic renewal is provided.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Moosend API key | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"path": {
"Page": 1,
"PageSize": 10
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List Moosend mailing lists — moosend.lists.list
Read one page of active email-list identities, names, status and subscriber-count summaries, together with the provider’s Paging metadata. Page is one-based. Advance it explicitly after inspecting TotalPageCount; no automatic paging, subscribers or imports are fetched.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.Page |
integer | Required | One-based page to request. | minimum: 1; maximum: 2147483647 |
path.PageSize |
integer | Required | Maximum list summaries on this page. This subset supports 1–100. | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"path": {
"Page": 1,
"PageSize": 10
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read a Moosend mailing-list summary — moosend.lists.get
Read one known list’s identity, name, status, subscriber counts and supplied creation/update timestamps. Requests WithStatistics=true. CreatedBy/UpdatedBy IPs, custom-field definitions, subscriber records, imports and preferences are excluded. No campaign send or list change occurs.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.MailingListID |
string | Required | The ID returned by lists.list for this account. | pattern: "^[A-Za-z0-9-]{1,128}$" |
Full JSON Schema
Example input
{
"path": {
"MailingListID": "04fad8e2-2b35-4302-a887-58f14a1152ab"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.