Skip to main content
You do not call these by name. Ask for what you want and the assistant picks the tool. The list is here so you know what is possible, and so you can nudge an assistant that reaches for the wrong thing. Every tool takes an optional workspace argument, the subdomain of a connected workspace. Left out, it uses the workspace the connection was set up with. What a tool returns depends on how you connected. Over OAuth, listings are filtered to what the approving person can see and a recording they cannot open is refused rather than returned; an API key reaches the whole workspace. A tool that writes or deletes is also refused when the connection was not granted that permission at approval time. See Authentication.

Recordings

Most of these tools are backed by the recordings endpoints. For field level detail, see the API reference.
DeleteRecording cannot be undone. Assistants are told it is destructive, but confirm what is about to be deleted before you approve the call.
search and fetch are the two tools the ChatGPT connector specification requires, so they overlap with SearchRecordingsByTitle / SearchRecordingsByTranscript and GetRecording rather than adding anything new. They have no separate REST endpoint, which is why they are not linked above.

Transcripts and chapters

Sharing and media

Folders and tags

Calls to action

Analytics

Recording requests

Public recordings

These reach recordings in other workspaces, and only when the recording is publicly accessible with no sign in required. They return less than their workspace counterparts, and they respect what the owner allowed, so a transcript or a download may be unavailable.

Workspaces