DEVELOPERS / DEVELOPERS
get_profile
Behavior, inputs, outputs and permissions for get_profile.
Reviewed · 2026-10-06 / Ridian
This reference is generated from the published tool contract.
Behavior and boundaries
Section titled “Behavior and boundaries”Returns the Ridian profile behind this connection: a stable opaque id and, when available, the display name and sign-in email. Use it to tell apart several connected Ridian accounts. Reads no calendar, task, contact or mail data.
Permissions
Section titled “Permissions”Granted scopes, accounts, calendars and visibility rules limit access. Workspace administrators do not automatically gain access to other users’ accounts.
calendar:read
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false}Output
Section titled “Output”{ "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "minLength": 1 }, "name": { "type": "string" }, "email": { "type": "string" } }, "required": [ "id" ], "additionalProperties": false}Errors and retries
Section titled “Errors and retries”Check the tool result for errors. Do not blindly retry writes after a timeout. Check the current resource or send status first.