machship-mcp

Delete Identities

machship_delete_identities

Destructive

Permanently delete specified identity IDs from Machship; this action cannot be undone.

Instructions

Delete the identities with the given IDs. This action is irreversible.

Args:

ids (number[]): Array of identity IDs to delete

Input Schema

Name	Required	Description	Default
`ids`	Yes	Identity IDs to delete

Output Schema

Name	Required	Description	Default
`errors`	No	Validation errors returned by Machship, if any
`object`	No	Response payload from the Machship API

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.1Nov 3, 2026

addedInput schema / properties / ids / items / maximum
```
Added value: +9007199254740991
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "errors": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Validation errors returned by Machship, if any"
+    },
+    "object": {
+      "description": "Response payload from the Machship API"
+    }
+  },
+  "type": "object"
+}

First observedv1.0.0Jun 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds the useful nuance that the deletion is irreversible, confirming there is no reenable path, but it says nothing about cascade effects (e.g. linked companies, public keys) or required permissions for a batch destructive operation.

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?

Two short sentences with the critical warning front-loaded; nothing is padded. The 'Args:' block duplicates schema information and is the only wasted element.

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?

An output schema exists and annotations carry the destructive/idempotency profile, so an agent has enough to call this correctly. For a batch irreversible delete, a sentence on what happens to dependent records would have made it 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?

Schema description coverage is 100% and the single 'ids' parameter is fully documented in the schema (array of positive integers, minItems 1). The description's Args block merely restates that without adding format, limits, or behavior for partial failures in a batch.

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?

States a specific verb ('Delete') and resource ('identities with the given IDs'), which is clearly distinct from the sibling family (get_identities, disable_identities, update_identity). It does not explicitly name the closest alternative (disable_identities), so it falls just short of full sibling differentiation.

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 'irreversible' note implicitly signals this is the hard-delete path rather than the reversible machship_disable_identities, but there is no explicit when-to-use/when-not guidance, no prerequisite or permission statement, and no warning about what else is removed.

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

Deploy Server