OutreachPilot MCP Server

delete_contact

Permanently remove a CRM contact by its ID. Requires confirmation; this action cannot be undone.

Instructions

Permanently delete a contact from the CRM by its ID. This cannot be undone.

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": {
      "contact_id": "<contact_id>"
    },
    "name": "delete_contact"
  }
}

Input Schema

Name	Required	Description
`confirmed`	No	Must be true to permanently delete the contact.
`contact_id`	Yes	ID of the contact 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/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the permanent, irreversible nature of the deletion, which is critical behavioral information. It does not mention the required confirmation parameter, but that is covered 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?

Two short sentences, directly to the point, with no filler. The description earns every word.

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 paired with the schema provides sufficient information for a destructive operation, including permanence and the confirmation flag. It lacks explicit alternatives or consequence handling, but for a simple delete tool this is adequate.

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 coverage is 100% with each parameter described. The description adds no parameter-specific details beyond mentioning the ID, so the baseline of 3 applies.

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 states 'Permanently delete a contact from the CRM by its ID', using a specific verb and resource, and clearly distinguishes from sibling tools like update_contact or create_contact.

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 use when a contact must be permanently removed, and the warning 'This cannot be undone' signals caution. However, it does not explicitly compare with alternatives or state conditions when not to use it.

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