Update GTM Context
Write changes to the GTM context your AI uses about your organization. Synthesizes unstructured content into structured offerings, personas, segments, and competitors, or makes direct edits to existing records. Free.
Rowan BaileySenior Director, Product
Overview
Hand the AI a battlecard and get structured GTM context back. Update GTM Context is the write companion to GTM Context: it reads raw material like a product brief or an interview transcript, distills the concepts inside, and files them against the right records. It also handles direct edits when you just want to archive a competitor or rename a segment.
What You'll Get
Structured records created or updated across whichever object types your material touches:
| Object | Captures |
|---|---|
| Company overview | Name, elevator pitch, description, strategic priorities, custom fields |
| Offerings | Products and services, value propositions, pain points, proof points, custom fields |
| Buyer personas | Roles, objectives, pain points, priorities, custom fields |
| Ideal customer profiles | Segments, company profile criteria, technologies used, custom fields |
| Competitors | Products, strengths, weaknesses, win/loss reasons, custom fields |
When source material includes something that fits no standard field, the agent creates a custom field rather than dropping it. Past examples include "integration timeline," "budget cycle," and "decision maker."
Best For
- Loading a competitive battlecard into GTM context
- Building buyer personas out of customer interview transcripts
- Keeping ICP definitions current as segmentation shifts
- Housekeeping: archiving a stale competitor, renaming a segment
To read your current context rather than change it, use GTM Context.
How It Works
The tool runs in two modes.
Synthesis
Supply a query describing your intent plus sourceMaterial, which can be battlecard text, a product brief, a transcript, or a brain dump. The agent reads the source, distills the GTM concepts, deduplicates against what already exists, and writes structured updates. One call can touch several object types. A competitive battlecard usually carries competitor intelligence, offering differentiation, and persona pain points all at once, and each concept routes to the record where it belongs.
Direct edit
Supply a query alone. The agent acts on existing records. Archive a competitor, rename a segment, restate an elevator pitch.
Technical Details
Credits
Free. Update GTM Context consumes no credits, even though each call runs a context agent that analyzes the input, deduplicates against existing context, and writes the changes. See Credits & Billing.
Requirements
The authenticated user must be a ZoomInfo admin. Standard users can read their GTM context but cannot modify it.
Parameters
| Parameter | Required | Description |
|---|---|---|
query | Yes | Natural language instruction framing the intent and scope of the update. |
sourceMaterial | No | Raw content to analyze. Limit ~2,000 words per call. For larger documents, break the work into multiple calls with scoped queries targeting different sections. |
Automatic Tool Selection
The AI reaches for this tool when you supply new material to load, or issue a direct change. For complex inputs the orchestrator may chain GTM Context to read current state, this tool to apply the change, then GTM Context again to verify. Longer source material gets chunked. Anything beyond roughly 2,000 words is split across several calls, each scoped to a different section, because tighter scope produces better synthesis than one overloaded call.
Architecture
Every record created or updated through this tool is tagged with its MCP provenance, which keeps agent-written GTM context distinguishable from manual entries.
Example Prompts
"Here's our latest competitive battlecard against our biggest competitor. Update our GTM context with the win/loss reasons and product comparisons."
"Create buyer personas from these three customer interview transcripts."
"Archive the Globex competitor record."
"Rename our 'Enterprise SaaS' ICP segment to 'Enterprise Software' and refresh the description."
In a first-time onboarding flow
Start by reading saved context. The prompt below begins with an account briefing, using the business context already available to your user. To change shared context later, an admin can supply source material and request an update to offerings, personas, or ICPs.
(Use the ZoomInfo MCP tools if available; otherwise use the GTM CLI. Use the tool schema or CLI help for supported commands.) I just connected ZoomInfo. Help me complete the job below. 1. Read my saved business context with get_gtm_context, or the CLI equivalent. This read is free. Use the returned offerings, ICP, and role to frame the work. If context is missing, continue with the information we have. Save changes only if I explicitly ask; a first briefing does not require updating shared business context. 2. Prepare a connected account briefing. Ask me only which company or domain to brief if I haven't named one. Use the account and decision already in this conversation when available. Connect the account's available CRM history, including stage and status, with recent customer conversations and external buying signals. Use Account Research, and add Browse Engagements, Conversation Intelligence, or company signals when the briefing needs more evidence. Return a short briefing: where things stand, what changed, what remains unresolved, and one recommended next action. Cite the source and date for each material fact when returned. Distinguish the recommendation from the evidence. 3. Before calling a tool, check its schema or documented inputs rather than guessing at parameters. Ask only for missing inputs, in a single message, then name the tools and give a credit estimate if supported by their documentation. Label it as an estimate: actual charges depend on records and work done. Ask for approval once before paid research, then complete the selected job. If a tool call comes back "No approval received" or a similar permission response, say so plainly, name the tool, and continue with the remaining steps. Don't retry the same call hoping for a different result, and don't invent an approval that didn't happen. Include a source-coverage note of no more than 3 lines. Separate an unavailable or unauthorized source from a successful search with no matching records. If connection status is unknown, say so. Never infer "no customer history" from an empty result. Continue with available evidence and identify what is missing; use https://gtm.ai/guides/connect-customer-context for source setup. Recommend CRM changes as drafts. Applying them requires an available, separately connected CRM workflow and my authorization. Do not claim a CRM update was made by ZoomInfo research tools.
New to ZoomInfo?