ClearScribe AI

Destructive: delete only the exact highlight shown in a fresh prepare result, after showing its preview and obtaining separate explicit customer approval. Pass the prepare token unchanged and reuse the prepare requestId. Never synthesize a token or retry with a new requestId. Expired, changed, or mismatched targets require a fresh preview and approval.

Permanently delete the exact prepared ClearScribe memory only after the user separately confirms its title and irreversible consequences. Use the same requestId, memoryId, expectedUpdatedAt, confirmationToken and confirmationPhrase returned by preparation. Never infer consent from preparation alone.

Destructive. Confirm only after separate explicit customer confirmation of the prepared tag deletion. Reuse its requestId, confirmationToken, and confirmationPhrase unchanged.

Correct an existing ClearScribe AI memory only after explicit user approval. First read the exact memory and use its updatedAt timestamp to prevent overwriting newer changes. Correction history is preserved.

Create a real Jira issue from one exact ClearScribe meeting Action Item. Call only after the customer explicitly requests creation and confirms the project and ticket details. ClearScribe verifies meeting ownership and Action Item membership, prepares the source-derived Jira content, and must grant a new durable claim before this tool calls Jira. Reuse the same requestId only for the identical request. Completed, claimed, failed, or uncertain operations never trigger a replacement Jira issue.

Create a manual ClearScribe meeting only when explicitly requested. Accept customer-provided details only; transcript, speakers, action items, and generated meeting intelligence are not created. Use an available meeting templateType when requested.

Create a meeting folder only when explicitly requested.

Create a transcript-backed highlight only after resolving the exact meeting, retrieving its stored transcript, locating the exact selected passage and actual speaker if available, presenting the proposed highlight, and obtaining explicit customer approval. Never paraphrase or invent speaker/timestamps; preserve missing timestamps as null. SaaS verifies the quote and speaker segment. Existing matches return duplicate=true, not a new creation.

Create a meeting tag only when explicitly requested.

Create a new ClearScribe AI memory only after the user explicitly requests and approves its exact title and content. Never save inferred personal information without approval. Uses an idempotent request ID.

Create a ClearScribe AI Note from customer-provided content. Call only after the customer explicitly asks to create the Note; set confirmed=true only after that request. The operation is idempotent for the same requestId and content.

Create a Read Aloud or AI Voice Briefing from an account-owned note, meeting, or memory. Use the voice and source options to resolve names; reuse requestId when retrying this same creation.

Create a general Jira issue using the authenticated account's existing Jira OAuth connection. For a ClearScribe meeting Action Item, do not use this generic tool; first use list_clearscribe_meeting_action_items, then create it with create_clearscribe_action_item_jira_ticket so ClearScribe verifies ownership and coordinates idempotency. Call this generic tool only for unrelated Jira work, after the customer explicitly requests creation and confirms the destination and details. This generic operation is not idempotent; do not retry if Jira's response is uncertain.

Permanently delete an account-owned SaaS ClearScribe Note only after explicit customer confirmation. First use list_clearscribe_notes to resolve the exact title and verify source is saas. Never call this for source=mcp or an ambiguous record.

Delete an eligible translation session owned by the connected ClearScribe account. Only call after the user explicitly asks to delete it; active sessions cannot be deleted.

Delete an eligible Voice session owned by the connected ClearScribe account. Only call after the user explicitly asks to delete it; active sessions cannot be deleted.

Read the durable status of one Action Item → Jira operation by its requestId. This tool never creates or retries a Jira issue. Use it to inspect completed, failed, processing, or uncertain operations before taking further action.

Read Auto-Join settings and scheduled Meeting Bot activity. Queued or scheduled does not mean joined or recording; botCreated and botStatus are separate facts. Does not change settings or create Meeting Bots.

Read actual Google and Microsoft Calendar connection status for the authenticated ClearScribe account. Returns localized guidance and a safe handoff to ClearScribe Meetings. Never includes credentials.

Show the connected status and reconnect guidance for Notion, Google Docs, Google Drive, Slack, and Jira. Credentials and access tokens are never returned.

Show recent account-owned export workflows, including provider, source, status, completion or failure, and safe retry guidance. Use limit to resolve requests such as recent or latest exports.

Find account-owned exportable Notes, Meetings, Memories, or Translations, available sections and formats, connected destinations, and recent workflow status. Use title/source-type query and date filters to resolve natural-language requests such as latest, yesterday, or a named document.

Discover ClearScribe Live Captions languages, multilingual support, features, the selected/default caption language, and localized guidance. Caption language choices come from ClearScribe’s live catalog and are not limited to the display-language list. ChatGPT cannot access your microphone.

Inspect the existing durable regeneration operation using the exact Meeting ID, locale, and request ID from the original request; validate its returned operation type and identity. This is read-only and never starts or retries generation. Preserve pending, processing, completed, and failed states; report partial completion and actual Action Item reconciliation/Signals-refresh outcomes. For PROCESSING_OUTCOME_UNKNOWN, state that the provider outcome and any charge are uncertain, preserve operation ID/error and recovery guidance, and do not start another operation or generate a fresh request ID.

Read the sharing status for one exact account-owned ClearScribe Meeting. Use Meeting discovery if its exact ID is unknown; ask the customer to choose if multiple Meetings match. Call this before changing or revoking sharing. Reports only an active signed URL explicitly returned by ClearScribe; expired, revoked, and missing shares have no accessible URL.

Read speaker labels and exact transcript segments for one exact meeting ID. Resolve natural-language date/title references with list_clearscribe_meetings first, and ask the customer to choose if several meetings match. Use returned segmentIndex, exact text, and available timestamps as the source snapshot; do not infer missing timestamps.

Read the status and result of a ClearScribe AI processing request. Returns pending, processing, completed, or failed, including the saved Note ID when available.

Read correction history, exact before/after snapshots, correction IDs, undo state, the latest active correction, and localized undo review guidance for one exact meeting ID. Resolve natural-language references with list_clearscribe_meetings first, clarify multiple matches, and never guess which correction to undo.

Find supported source and target languages and the connected user's available Notes, Meetings, and AI Memory sources. Use this to resolve natural-language references like 'my latest meeting' before translating.

Show recent translations, or retrieve one translation by sessionId. Completed translations include the translated text; failed sessions include the next action.

Find supported languages, available voices, and the connected user's account-owned Notes, Meetings, and AI Memory sources. Use source titles and voice names to handle natural-language requests.

Show recent Voice sessions, or retrieve one session by sessionId. Ready sessions provide authenticated playback and download handoffs; private audio URLs are never returned.

List upcoming events from Calendars already connected through ClearScribe. Events without a meetingUrl are not eligible for Auto-Join. Provider partial failures and source attribution are preserved; times are returned exactly as supplied by Calendar providers.

List the saved ClearScribe Action Items for one exact meeting. Resolve the meeting with ClearScribe meeting discovery first. Use exact returned Action Item IDs and ask the customer to choose if multiple items match. To create a Jira issue from a selected item, use create_clearscribe_action_item_jira_ticket, never the generic create_jira_ticket tool. If Jira lookup is unavailable, report that fact and do not imply an item has no Jira link.

Read existing account-owned ClearScribe Meeting Bot lifecycle records, including historical Auto-Join and saved Meeting records. Use exact status strings from discovery; no Bot lifecycle changes are performed.

List the connected customer's ClearScribe meeting folders. Use returned IDs; never invent folder IDs.

List actual saved highlights for one exact ClearScribe meeting. Resolve natural-language meeting references with meeting discovery first; ask the customer to choose if multiple meetings match. Returns an empty list when the meeting has no saved highlights.

List the connected customer's ClearScribe meeting tags. Use returned IDs; never invent tag IDs.

List the connected user's account-owned ClearScribe meetings, including IDs, status, folders, tags and safe website links. Filter by keyword, date range, archive state, source type, folder, tags, or processing status. Date, source-type and processing-status filters apply across sources. Archived-only, folder, tag and nonzero offset filters search SaaS only; the response identifies excluded sources. Each meeting includes its source (mcp, saas, or linked_device); pass that source to ask_clearscribe_meeting when asking about a specific meeting. MCP and SaaS meetings with the same ID are separate results. For linked-device meetings, preserve the sourceKey unchanged. If several meetings match a natural-language reference, ask the customer to choose an exact meeting before writing.

List or search the connected customer's ClearScribe AI memories. Returns previews, IDs, statuses, timestamps and pagination. Use read_clearscribe_memory for full content.