Prompts

Use built-in Saber MCP prompt templates for common sales intelligence workflows such as company research and contact enrichment.

Prompts are reusable message templates your AI client can invoke by name. They set up the context and tool sequence for common Saber workflows, so you don't have to describe the steps each time.

Invoke a prompt by name in your AI client — for example, in Claude Code: /mcp__saber__research-account.

Research account

Research a company before a sales call. Runs key signal questions in parallel, then generates a consolidated brief.

Arguments:

ArgumentRequiredDescription
domainYesThe company's website domain (e.g. acme.com) — no https:// or www.
focusNoOptional focus area (e.g. "tech stack", "hiring trends", "funding status"). Leave blank for a general overview.

What it does:

  1. Runs createCompanySignal in parallel for: company overview, revenue, funding, engineering team size, tech stack, hiring trends, and recent news
  2. Calls generateSignalSummary to consolidate the signals
  3. Returns a structured sales brief with: Company Overview, Technology, Growth & Hiring Signals, Recent Activity, Buying Signals, and Recommended Talking Points

Qualify account

Qualify a company against your ICP criteria and return a scored verdict with evidence.

Arguments:

ArgumentRequiredDescription
domainYesThe company's website domain (e.g. acme.com)
criteriaNoYour qualification criteria as a description or list (e.g. "Series A or later, 50–500 employees, uses Salesforce, US-headquartered"). If not provided, the assistant will ask before proceeding.

What it does:

  1. For each criterion, runs createCompanySignal with a focused question to gather evidence
  2. Returns a Verdict (Qualified / Needs Review / Disqualified), a criterion-by-criterion breakdown table, and a 2–3 sentence summary

Research contact

Research a contact before a meeting. Gathers LinkedIn insights and surfaces personalised conversation openers.

Arguments:

ArgumentRequiredDescription
linkedin_urlYesThe contact's LinkedIn profile URL (e.g. https://linkedin.com/in/janedoe)
company_domainNoThe contact's company domain (e.g. acme.com). Enables additional company-level context.

What it does:

  1. Calls createContactResearch with the LinkedIn URL and polls until complete
  2. Optionally runs createCompanySignal to understand the company context in parallel
  3. Returns a contact brief with: Background, Expertise & Interests, Likely Pain Points, Conversation Openers, and Things to Avoid

On this page