get_user_permissions
Read one principal's current Play Console permissions by email — read-only, nothing changes. Works for a human teammate or a service account (…@….iam.gserviceaccount.com); both are the same user row keyed by email. Returns account-level permissions and, per app, the exact permission values already held. This is the prerequisite before grant_app_permission: an append has to preserve every app the principal already reaches, so read the current grants first and confirm them with the user.
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": {
"developer_id": "<developer_id>",
"google_account_email": "<google_account_email>",
"target_user_email": "<target_user_email>"
},
"name": "get_user_permissions"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| developer_id | Yes | Numeric Play Console developer id (from the Play Console URL). | |
| target_user_email | Yes | The email whose permissions to read — e.g. the CI service account …@….iam.gserviceaccount.com. | |
| google_account_email | Yes | The signed-in Google account email that owns this Play Console developer account (the one acting). Call list_accounts first and confirm with the user — do not guess. | |
| notification_message | No | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |