Sends transactional email through Amazon SES v2. Requires a verified sending identity and IAM credentials with the ses:SendEmail permission.
Example workflows
Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.
Send email
Help me with this task in Amazon SES: Send email. Ask me to choose the destination and provide the content and any required resource IDs. Show the exact proposed change for my review, then perform it only after I approve. Return the created or updated resource ID and link when supplied. If the result is uncertain, inspect it before attempting the same change again.
Explore this command: amazon-ses.send
What you can do (1)
What you can do
Available commands: 1 (0 read, 1 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Send email — amazon-ses.send |
Write |
Connect and use
Tooluse.net supplies the provider credentials for these commands. You do not need to apply for a provider API key. Select Tooluse.net credentials in the connection form; complete provider sign-in or authorization if prompted.
Connect this integration, select Tooluse.net credentials, choose the commands you need and save. Complete provider sign-in if prompted.
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": {
"from": {
"address": "[email protected]",
"name": "Planner.li"
},
"to": [
{
"address": "[email protected]",
"name": "Example user"
}
],
"replyTo": [
{
"address": "[email protected]"
}
],
"subject": "Your trip is confirmed",
"text": "Hello — your trip is confirmed. Sign in at https://planner.li to see the full itinerary.",
"html": "<p>Hello — your trip is confirmed.</p><p><a href=\"https://planner.li\">See the full itinerary</a></p>",
"headers": {
"X-Entity-Ref-Id": "trip-2026-09-09-0001"
},
"tags": {
"campaign": "trip-confirmation"
}
}
}'
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
Send email — amazon-ses.send
Run Send email with Amazon SES. This command can change provider data. Review the target and input before invoking it.
This operation can change provider data. Review the input before allowing an agent to call it.
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 |
|---|---|---|---|---|
from |
object | Required | additionalProperties: false |
|
from.address |
string | Required | maxLength: 320; format: "email" |
|
from.name |
string | Optional | maxLength: 200 |
|
to |
array | Required | minItems: 1; maxItems: 50 |
|
to[] |
object | Optional | additionalProperties: false |
|
to[].address |
string | Required | maxLength: 320; format: "email" |
|
to[].name |
string | Optional | maxLength: 200 |
|
cc |
array | Optional | maxItems: 50 |
|
cc[] |
object | Optional | additionalProperties: false |
|
cc[].address |
string | Required | maxLength: 320; format: "email" |
|
cc[].name |
string | Optional | maxLength: 200 |
|
bcc |
array | Optional | maxItems: 50 |
|
bcc[] |
object | Optional | additionalProperties: false |
|
bcc[].address |
string | Required | maxLength: 320; format: "email" |
|
bcc[].name |
string | Optional | maxLength: 200 |
|
replyTo |
array | Optional | maxItems: 5 |
|
replyTo[] |
object | Optional | additionalProperties: false |
|
replyTo[].address |
string | Required | maxLength: 320; format: "email" |
|
replyTo[].name |
string | Optional | maxLength: 200 |
|
subject |
string | Required | minLength: 1; maxLength: 998 |
|
text |
string | Required | minLength: 1; maxLength: 200000 |
|
html |
string | Optional | minLength: 1; maxLength: 1000000 |
|
attachments |
array | Optional | maxItems: 5 |
|
attachments[] |
object | Optional | additionalProperties: false |
|
attachments[].filename |
string | Required | maxLength: 255; pattern: "^[A-Za-z0-9][A-Za-z0-9._ -]{0,253}[A-Za-z0-9]$" |
|
attachments[].contentType |
string | Required | maxLength: 78 |
|
attachments[].contentBase64 |
string | Required | minLength: 4; maxLength: 131072; pattern: "^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$" |
|
headers |
object | Optional | maxProperties: 20; additionalProperties: {"type":"string","maxLength":1000} |
|
tags |
object | Optional | maxProperties: 10; additionalProperties: {"type":"string","maxLength":256} |
Full JSON Schema
Example input
{
"from": {
"address": "[email protected]",
"name": "Planner.li"
},
"to": [
{
"address": "[email protected]",
"name": "Example user"
}
],
"replyTo": [
{
"address": "[email protected]"
}
],
"subject": "Your trip is confirmed",
"text": "Hello — your trip is confirmed. Sign in at https://planner.li to see the full itinerary.",
"html": "<p>Hello — your trip is confirmed.</p><p><a href=\"https://planner.li\">See the full itinerary</a></p>",
"headers": {
"X-Entity-Ref-Id": "trip-2026-09-09-0001"
},
"tags": {
"campaign": "trip-confirmation"
}
}
At most 1 provider requests per invocation; timeout: 20 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.