OutreachPilot MCP Server

onboarding_guide

Get a step-by-step onboarding guide to set up OutreachPilot from scratch, covering account setup, email connection, ICP configuration, knowledge base, contacts, campaigns, and launch.

Instructions

Get the step-by-step onboarding guide for setting up OutreachPilot from scratch. Returns a detailed walkthrough covering: account setup, email connection, ICP configuration, knowledge base, contact import, folder organization, campaign creation, and launch. Use this when a user is new or asks how to get started.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "onboarding_guide"
  }
}

Input Schema

Name	Required	Description	Default
`focus`	No	Optional: Focus on a specific area. Options: email, icp, knowledge_base, contacts, campaigns, integrations, all. Default: all.	all

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Aug 9, 2026

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. It discloses that the tool 'Returns a detailed walkthrough' and enumerates covered topics, but it doesn't explicitly state that it has no side effects or mutations. Adequate for a read-only guide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with a useful enumerated list of content areas. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple informational tool with one optional parameter and no output schema, the description covers the purpose, content areas, and usage context. Complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole optional parameter 'focus' is fully documented in the schema with options and default (100% coverage). The description doesn't add extra parameter context, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get the step-by-step onboarding guide for setting up OutreachPilot from scratch' with a specific verb and resource. It distinguishes from sibling tools by being the only onboarding/setup guide among data operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use this when a user is new or asks how to get started,' providing clear context. It doesn't mention exclusions, but none are necessary given the tool's informational nature.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.