Read sign-in email setup
appAuthEmailStatusRead one owned app’s sign-in email setup, as its Email page shows it: its resolved sender, the email provider’s identity for the app’s own domain, and the DNS records, all under send.<domain>, each with relativeName, the name a zone editor takes. It writes nothing and asks the provider nothing but a read. The result’s state distinguishes the observations: configured means a live read of the app’s auth service returned the resolved sender; not_configured, it was read and carries another sender (or none), or Tofu cannot set one yet; disabled, this deployment sends no app mail (the app is unaffected and keeps sending its own mail); unavailable, the read produced NOTHING, which says nothing about the app. Nor does an email provider that was not reached (records is then empty). sender is resolved from what the provider really reported, never a sender that has not moved: a domain whose records were written but not yet observed is NOT connected.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>"
},
"name": "appAuthEmailStatus"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dns | Yes | ||
| state | Yes | ||
| domain | Yes | ||
| sender | Yes | ||
| appName | Yes | ||
| enabled | Yes | ||
| message | Yes | ||
| records | Yes | ||
| siteUrl | Yes | ||
| identity | Yes | ||
| nextSteps | Yes | ||
| observedSender | Yes |