get_gtm_profile

The user’s own GTM profile — ICP, market, product, pricing, competitors, positioning. Workspace-level, NOT per-entity.

The meta-tool. Where get_account / get_context return facts about a person or company, this returns the workspace owner’s own GTM profile — what they sell, who to, pricing, and positioning — the context your agent should reference when answering “what’s our ICP?” or “what differentiates us?”

Formerly get_workspace_facts — that name still works as an alias.

Parameters

Name	Type	Required	Description
categories	string[]		Optional filter (e.g. ["ICP"] or ["Pricing","Competitors"]). Omit for all.
limit	number		Max facts. Default 50, cap 500.

Common categories: ICP, Market, Product, Pricing, Competitors, Playbook. Users can add any custom category in the in-app GTM Context tab.

Returns

Grouped by category:

ICP (2):
  GTM Engineers or RevOps leaders at B2B SaaS, 50-200 employees, US.  [3h ago]
  We focus on teams already using Apollo + Smartlead.                  [2d ago]

PRICING (1):
  Free self-host. Scale $99/mo. Agency $499/mo.                       [5d ago]

If nothing’s recorded:

No GTM profile recorded yet. The user can set it up in the GTM Context tab.

When to call it

• “What’s our ICP?” → categories: ["ICP"]
• “What’s our pricing strategy?” → categories: ["Pricing"]
• “What differentiates us from competitors?” → categories: ["Competitors", "Product"]
• “Show me the whole GTM profile” → no filter

When NOT to call it

Anything about a specific person or company — use get_context or get_account. Anything about activity across many entities — use query.

Why it exists

When the agent drafts personalised outreach, it needs BOTH:

• The contact’s context (get_context) — what’s true of THEM
• The user’s GTM profile (get_gtm_profile) — how WE sell

Combine the two and the agent has everything to write natural copy.

Backed by

GET /v2/workspace/facts — see the HTTP reference for the raw JSON shape.