ChatGPT Plugin

Call Trace

Review calls and transcripts

Brand: Unknown

Category: Pending
Primary Subcategory: Pending

Integration details

Description

Connect an authenticated Call Trace workspace to list minimal call metadata and retrieve a redacted transcript for a specific recording. The plugin is read-only, tenant-scoped, and returns only the fields needed for these user-requested actions.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-10-31
Tool count: 3
Market: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

Sign up to track your Plugin See who ChatGPT suggests

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Call Trace has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

3 tools agents can invoke

Retrieve minimal processing metadata for one explicitly requested call in the authenticated Call Trace workspace.
get_call
Retrieve the text transcript for one explicitly requested call in the authenticated Call Trace workspace. Common contact, payment, government-ID, and credential-like values are redacted.
get_transcript
List minimal metadata for call records in the authenticated Call Trace workspace by status, queue, date, or an explicit recording reference.
search_calls

FAQs

Call Trace ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Call Trace's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.