Skip to main content
Writes to your heyBTW workspace. With confirm: true it saves the target spec for one scope, replacing that scope’s block and keeping the prior version. Without confirm it saves nothing. It sends nothing.
This tool is evolving. This page describes what the connector serves today and will be revised as the tool changes.
A target spec says who belongs at your events: titles, seniority, kinds of companies, a city, and exclusions. Save it once for the workspace, and per collab when one event differs. Every invite sprint then starts from it. Follows the heyBTW MCP rules.

When to use it

  • “Our events are for VP and above in RevOps and Marketing at 50 to 500 person SaaS companies.”
  • “For the LA dinner, only people within 50 miles, and no current customers.”
  • get_workspace_overview or get_event_details served target_spec: null with a next step to save one.

Parameters

The target_spec block is an object with these keys:
  • describe: free text.
  • personas: a list of objects, each with titles, seniority and functions.
  • companies: an object with industries, size_bands, regions, tech and funding_stage.
  • exclusions: an object with customers, competitors and partner_employees.
At collab scope only, it also takes:
  • geography: an object with city and radius_miles. The default is the collab’s city and 50 miles.
  • target_account_sources
  • net_new_goal
  • exclusions.invited_no_show_min
  • seniority: c_suite, vp, director or manager, as a floor (director means directors and above). A single string is read as a one-item list.
  • regions: North America, LATAM, EMEA, APAC, ANZ, Middle East, Africa or Global, where a company is headquartered.
  • size_bands: "min-max" or "min+", for example "50-500".
  • geography is where the people must be, never a company headquarters.

Workflow

1

Ask the user who they want

Do not derive a spec from the roster or the CRM.
2

Preview

Call without confirm. The response shows the resolved spec, which keys change and every item left out with its allowed values.
3

Confirm

After the user agrees, call again with the same spec, confirm: true and a fresh client_request_id. On a transport error, retry with the same id: a committed save is replayed, never repeated.

Response

Neither a preview nor a save was captured for this page. The shape below is from the tool’s code and contract.

Rules the agent must follow

  • Preview first. Save only after the user agrees.
  • The spec is membership criteria only. heyBTW grades, tiers and ranks no one from it and runs no search.
  • Take search_brief to the user’s own tools. suggested_sources are suggestions, not steps.
  • No spec is shared with a partner.

Errors and gaps

This validation error is real, captured today from a call with no parameters.
  • entity_not_found: a partner’s collab, the demo collab or an unknown channel_id.
  • insufficient_scope: the OAuth token lacks mcp:tools:write. Nothing is saved.
  • An unknown seniority is rejected on its own; the rest still saves.