for gtm engineers
The LinkedIn leg of your agent stack
You've built the enrichment flows and the signal watchers. The missing leg is LinkedIn execution that won't torch a seat. LinkedBoost is that leg: 58 typed tools, envelope responses, and guardrails enforced server-side: because the model will do whatever the tools allow.
Every capability is a typed MCP tool returning a structured envelope: result, signals, learnings. Claude-first; composes with the rest of your stack.
Caps, ramps, suppression, and collision rules live in the server. Your agent can't be prompt-injected into burning an account.
Lead groups, contacted-universe memory, and workspace knowledge survive across sessions: strategy as files, not vibes.
What you'd run first
Hiring signals and post activity → sourced, filtered, drafted, queued for approval.
LinkedIn state feeds your email stack; replies land back in one inbox.
Read the tool reference: every tool documents what you'd say to Claude to invoke it.
Browse all 58 tools in the docs: each with envelope semantics and a real example prompt. No black box.