OutreachPilot MCP Server

delete_company

Permanently delete a company account from the CRM. Contacts linked to the company are unlinked but not deleted.

Instructions

Permanently delete a company account from the CRM. Contacts linked to this company will be unlinked but not deleted.

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": {
      "company_id": "<company_id>"
    },
    "name": "delete_company"
  }
}

Input Schema

Name	Required	Description
`confirmed`	No	Must be true to permanently delete the company.
`company_id`	Yes	ID of the company to delete.
`idempotency_key`	No	Optional stable key to prevent duplicate delete attempts on retries.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Aug 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the action is 'Permanently' destructive and describes the side-effect that linked contacts are 'unlinked but not deleted.' This is valuable behavioral context, though it could also mention the confirmed flag requirement, which is in the schema.

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 with no redundancy. The first sentence delivers the core purpose, and the second adds a critical side-effect in a clear, front-loaded manner.

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

Completeness4/5

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

The description, combined with the schema's detailed parameter documentation, provides sufficient context for safe usage. It covers irreversibility and side-effects, making the tool adequately understandable. The confirmation flag is documented in the schema, so the description does not need to repeat it.

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 for all three parameters, so the description does not need to add parameter-level details. It does not discuss parameters, but the schema already provides full meanings. 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 'Permanently delete a company account from the CRM' with a specific verb and resource, distinguishing it from sibling tools like delete_contact by focusing on company accounts. It also explains the effect on linked contacts, further clarifying its unique purpose.

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 provides clear context that this tool is for deleting a company, with no ambiguity about its use case. It mentions the unlink side-effect, but does not explicitly name alternatives or when-not-to-use scenarios. The context is apparent given the tool name and description.

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