MCP TOOLcubeshell.email.personal.find

Find Personal Email

Finds the personal, non-work email address of one person identified by their professional profile URL. It returns the primary personal address plus any additional personal addresses on record, or a not_found result. It does not find work emails, which is cubeshell.email.find, verify an address you already have, which is cubeshell.email.verify, or accept a name without a profile URL.

!
Personal contact data
This tool returns someone's personal address rather than their business one. Confirm your use case and the rules that apply to it permit personal contact data before you call it.

Request

Workspace identity comes from the authenticated MCP connection, not from the call arguments. There is no workspace field to set.

ParameterTypeDescription
request_idrequiredstringStable idempotency key, 1 to 200 characters. Replaying the same request_id with the same input returns the original result without a second charge.
quote_onlyrequiredfalseMust be false. Quote-only preview is not available in this version.
input.profile_urlrequiredstringProfessional profile URL or profile username, up to 500 characters. This identifies the one person to look up.
max_microcreditsintegerOptional ceiling. If the authoritative price is higher, the call is rejected before anything is charged.
tools/call
{
  "name": "cubeshell.email.personal.find",
  "arguments": {
    "request_id": "find-personal-email-001",
    "quote_only": false,
    "input": { "profile_url": "https://www.example.com/in/ada-lovelace" }
  }
}

Result

On status: "succeeded", the result field holds the addresses found.

ParameterTypeDescription
result.primary_emailstringThe main personal email address on record for that person.
result.emailsstring[] | nullAny additional personal addresses on record. Null when there are none beyond the primary address.

When no email exists

When no personal email exists for that profile, the response comes back with status: "not_found" and no result.primary_email. This is a real terminal status, not an error. The input was valid and the lookup ran to completion. It simply found no address for that person, and a not_found result is not charged.

Agents should treat not_found as the answer and move on. Retrying the same profile URL will not produce a different result.