OutreachPilot MCP Server

create_contact

Create contacts in the CRM, auto-create their company, and optionally enroll them in a campaign.

Instructions

Create one or more contacts in the CRM. Automatically creates the company account if a company is specified. Optionally enroll in a campaign immediately.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contacts": "<contacts>"
    },
    "name": "create_contact"
  }
}

Input Schema

Name	Required	Description
`upsert`	No	If true, update existing contacts instead of returning a duplicate error. Default false.
`contacts`	Yes	Array of contacts to create. Each contact requires email or linkedin_url.
`campaign_id`	No	Optional campaign ID to automatically enroll the created contacts.
`idempotency_key`	No	Optional stable key to prevent duplicate contact creation on retries.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Aug 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosing side effects. It discloses auto-creation of companies and optional campaign enrollment, but does not mention the upsert behavior (updating vs duplicate error) or idempotency semantics, which are significant behavioral traits.

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?

The description is two sentences, front-loaded with the main action, and every sentence adds meaningful context. No fluff or redundancy.

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

Completeness3/5

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

The description covers the main purpose and two side effects, but omits important context like duplicate handling, upsert behavior, and return values. Given the tool's complexity (4 params, nested array) and lack of annotations/output schema, more detail would improve completeness.

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?

Schema description coverage is 100%, so baseline is 3. The description adds minimal value beyond the schema: it restates campaign enrollment and company creation, but these are already described in the property descriptions. No additional parameter meaning is provided.

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 the action (create), the resource (contacts), and the scope (one or more). It also distinguishes itself from sibling tools by mentioning automatic company creation and campaign enrollment, which are unique behaviors.

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

Usage Guidelines3/5

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

The description implies when to use this tool (creating contacts) and gives context that company creation is handled automatically, but it does not explicitly compare with alternatives like create_company or update_contact. No direct 'use this instead of X' guidance is provided.

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