SmartSuite MCP Server

smartsuite_list_deleted_records

Read-only

List soft-deleted SmartSuite records in a solution's trash, optionally filtered by application, to find record IDs for restoration.

Instructions

List soft-deleted records in a solution's trash (read-only). Solution-scoped — spans all applications in the solution; pass applicationId to filter to one. Returns id, title, applicationId, applicationName, deletedBy (member id), and deletedAt. Use the returned ids with smartsuite_restore_records. Respects allow/deny lists.

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": {
      "solutionId": "<solutionId>"
    },
    "name": "smartsuite_list_deleted_records"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	Pagination cursor (next_cursor from a previous response).
`fields`	No	Optional extra field slugs to include per deleted record.
`pageSize`	No	Max deleted records to return (default 100).
`solutionId`	Yes	The solution ID whose trash to list.
`applicationId`	No	Optional: only return deleted records from this application.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.8Jul 29, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, so the read-only mention is redundant. The description adds useful behavioral context about returned fields and permission respect, but lacks details on pagination behavior beyond 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 concise (4 sentences) and front-loaded with purpose. Every sentence adds value, with no redundancy.

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?

Given no output schema, the description adequately explains return fields and suggests follow-up use. Missing details like sorting or limits, but sufficient for a list tool.

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%, so baseline 3. The description repeats some schema info (required solutionId, optional applicationId, cursor for pagination) but adds minimal new meaning. No significant extra value.

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 the tool lists soft-deleted records in a solution's trash, specifying it as read-only. It distinguishes from sibling tools by focusing on deleted records and clarifying solution-scoped behavior.

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 explicit guidance: solution-scoped, optional applicationId filter, and relevance to smartsuite_restore_records. It could improve by contrasting with list_records for non-deleted records, but overall good.

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

Deploy Server