Tool Name: generate_brief
Description:
The `generate_brief` tool creates comprehensive summarized briefs about CRM entities
(accounts, deals, or contacts) by analyzing Gong activities within a specified time period.
Unlike `ask_account` and `ask_deal` which answer specific questions, this tool generates structured
summaries across multiple predefined categories.
It produces comprehensive insights organized into different categories such as key themes,
stakeholders, risks, next steps, and other relevant aspects of the entity's activities.
The workspace field is optional. If the account has exactly one Gong workspace it is
selected automatically. If multiple workspaces exist, provide either a numeric workspace
ID or an exact workspace name (case-insensitive).
When to use:
- When you need a comprehensive overview of an entity's recent activities.
- To generate structured summaries for account/deal reviews or handovers.
- When you want insights across multiple categories rather than answers to specific questions.
- For creating executive summaries or briefing documents.
When NOT to use:
- When you need answers to specific, targeted questions about a single account or deal. Use `ask_account` for account-scoped questions and `ask_deal` for deal-scoped questions.
- Do NOT use to fetch raw data such as transcripts, message bodies, or activity lists.
- Do NOT use for analytics across multiple entities or workspace-level reporting.
- Do NOT use to modify entity data or trigger workflows.
Key Characteristics:
- Read-only: The tool never modifies data.
- Time-bounded: Considers only calls and messages within the specified date range.
- Multi-category: Provides insights across multiple predefined categories.
- Structured output: Returns organized summaries rather than free-form answers.
Response Handling:
The response is a curated Gong summary. Present all sections and items verbatim.
Do not summarize or reorganize the content. Show call titles as clickable links and
include a source count per section. Expand email details only when the user requests it.
Format for readability.
Supported Entity Types:
- ACCOUNT: For CRM accounts/companies
- DEAL: For CRM deals/opportunities (name or CRM ID)
- CONTACT: For CRM contacts/leads (CRM ID only — name resolution not supported)
Supported Period Types:
- CUSTOM_RANGE: Use specific fromDateTime and toDateTime
- LAST_7DAYS: Activities from the last 7 days
- LAST_30DAYS: Activities from the last 30 days
- LAST_90DAYS: Activities from the last 90 days
Usage Tips:
- `crmEntity` accepts the entity name or CRM ID for ACCOUNT and DEAL. Name lookup uses exact
matching — provide the full name as it appears in the CRM. For CONTACT, provide the direct
CRM contact ID. If multiple matches are found, a clarification response is returned.
- For ACCOUNT, entity names must be provided in full — partial matches are not supported.
Name lookup uses exact matching — provide the full name as it appears in the CRM.
- If your account has two or more workspaces, providing the workspace parameter is mandatory.
Supply either a numeric workspace ID (e.g. "1234567890") or a workspace name
(case-insensitive, e.g. "Sales"). If the value parses as a number it is used as a
workspace ID; otherwise it is resolved as a workspace name.
- periodType is optional — defaults to LAST_90DAYS if omitted. Use CUSTOM_RANGE with
specific fromDateTime/toDateTime for a custom window.
- briefName must exactly match the name of a published brief in the Gong workspace.
It is a lookup key, not a free-text label. If the name does not match, the tool returns
an error listing the available brief names and their descriptions so you can choose the
correct one.
Clarification Flow:
When multiple CRM entities match the given name, the tool returns an error result containing
a JSON list of matches sorted by most recent activity. Each match has three fields:
- crmId: use this value as crmEntity when re-calling the tool.
- name: the entity name in CRM.
- lastActivity: ISO 8601 timestamp of the most recent Gong activity, or null if unknown.
Present the matches to the user — highlight entities with a recent lastActivity as active —
ask them to pick one, and re-call with the chosen crmId. This applies to ACCOUNT and DEAL entity types.
Not Found Flow:
When no CRM entity matches the given name or ID, the tool returns an error with
reason=CRM_ENTITY_NOT_FOUND. Inform the user that the entity was not found and ask them
to verify the name or ID as it appears in their CRM, then re-call with the corrected value.
Brief Name Resolution:
When the provided briefName does not match any published brief in the workspace, the tool
returns an error whose message contains the list of available briefs.
Each brief has a name and a description. If the user's input is similar to one of the
available brief names, re-call with the correct briefName. Otherwise, present BOTH the name
and the description for each brief to the user so they can pick the right one, then re-call
with the chosen briefName. Do NOT attempt to generate a brief with an incorrect name.
Example requests:
-----------------
Example 1 — Account brief using a name
----------------------------------------
{
"workspace": "Sales",
"briefName": "Business Goals",
"entityType": "ACCOUNT",
"crmEntity": "Acme Corp"
}
Example 2 — Deal brief using a CRM ID with custom date range
--------------------------------------------------------------
{
"workspace": "Enterprise",
"briefName": "Decision Criteria",
"entityType": "DEAL",
"crmEntity": "006EXAMPLE00001",
"periodType": "CUSTOM_RANGE",
"fromDateTime": "2025-07-01T00:00:00Z",
"toDateTime": "2025-09-01T00:00:00Z"
}
Example 3 — Deal brief using a deal name
------------------------------------------
{
"workspace": "Sales",
"briefName": "Decision Criteria",
"entityType": "DEAL",
"crmEntity": "Acme Corp - Annual Renewal"
}
Example 4 — Contact brief (CRM ID required)
--------------------------------------------
{
"workspace": "Sales",
"briefName": "Key Players",
"entityType": "CONTACT",
"crmEntity": "0035g00000DEFghiJKL"
}
Example 5 — Omitting workspace (single-workspace account)
----------------------------------------------------------
{
"briefName": "Progress Indicators",
"entityType": "ACCOUNT",
"crmEntity": "Acme Corp"
}
generate_brief
View in the ChatGPT registry