SmartSuite MCP Server

smartsuite_delete_records

Destructive

Delete SmartSuite records by ID with soft-delete to trash, requiring readwrite or admin mode and delete enablement; supports dry-run and returns deleted record IDs for recovery.

Instructions

Delete records (soft-delete to the trash). Requires readwrite or admin mode AND SMARTSUITE_ENABLE_DELETE=true. Supports dry-run. The response returns the deleted recordIds; they can be recovered with smartsuite_restore_records (when SMARTSUITE_ENABLE_RESTORE=true) or listed via smartsuite_list_deleted_records.

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": {
      "applicationId": "<applicationId>",
      "recordIds": "<recordIds>"
    },
    "name": "smartsuite_delete_records"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	If true, show what would be deleted without deleting (default true)
`confirm`	No	Must be true to execute deletion
`recordIds`	Yes	IDs of records to delete
`applicationId`	Yes	The application ID
`confirmationText`	No	Must match exactly: "DELETE N RECORDS" where N is the count

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.8Jul 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already indicate destructiveHint=true; the description expands on this by detailing soft-delete to trash, mode and env var requirements, dry-run support, return value (deleted recordIds), and recoverability via other tools. No contradiction with annotations.

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 long, front-loads critical information (soft-delete, mode, env var), and avoids redundancy. Every sentence adds value.

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

Completeness5/5

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

Given no output schema, the description covers prerequisites (mode, env var), behavior (soft-delete, dry-run), return value (recordIds), and recovery options. For a delete tool with five parameters, this is comprehensive and contextually 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%, so baseline is 3. The description adds minimal parameter-specific context beyond mentioning dry-run support; the schema already covers all parameter meanings adequately.

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 explicitly states the tool deletes records via soft-delete to the trash, specifies required mode and environment variable, and distinguishes itself from siblings by referencing recovery and listing tools. This provides a clear and specific 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 mentions required mode and env var, supports dry-run, and names alternative tools for recovery and listing, giving good context on when to use this tool versus alternatives. It does not explicitly state when not to use, but the alternatives imply it.

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

Deploy Server