OutreachPilot MCP Server

create_company

Create company accounts in the CRM. Supports batch creation, upsert to update existing records, and idempotency keys to prevent duplicates.

Instructions

Create a company account in the CRM.

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": {
      "companies": "<companies>"
    },
    "name": "create_company"
  }
}

Input Schema

Name	Required	Description
`upsert`	No	Update matching companies instead of erroring. Default false.
`companies`	Yes	Array of companies to create. Each requires name or domain.
`idempotency_key`	No	Optional stable key to prevent duplicate company creation on retries.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Aug 9, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the action 'create' and provides no information about side effects, permissions, or special behaviors like upsert or idempotency, which are defined in the schema but never surfaced. This is a complete lack of transparency.

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

Conciseness4/5

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

The description is extremely concise at one sentence with no wasted words, but it is so brief that it misses opportunities to convey useful context without bloat. It earns a 4 rather than a 5 due to the lack of value-added detail.

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

Completeness2/5

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

The tool has 3 parameters including an upsert flag and idempotency key, which are behaviorally significant. The description makes no mention of these features, nor does it describe return values or error conditions. With no output schema and no annotations, the description is incomplete for a tool with this complexity.

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 schema has 100% description coverage, so all parameters are already well-documented. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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

Purpose4/5

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

The description 'Create a company account in the CRM' uses a specific verb and resource, making the primary purpose clear. However, it does not differentiate from sibling tools like create_contact or create_webhook, which share the same 'create' pattern.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor are any prerequisites, exclusions, or typical use cases mentioned. The description is purely declarative and leaves the agent without selection criteria.

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