Skip to main content
Glama

List Deleted Entries

list_deleted_entries
Read-onlyIdempotent

List recently soft-deleted entries so you can identify and restore them, with optional workspace or project filters.

Instructions

List recently soft-deleted entries that can be restored

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_deleted_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
use_test_dbNo
workspaceIdNoWorkspace identifier alias
workspace_idNoFilter by workspace ID, or "*" for all workspaces
projectNumberNoProject number alias
project_numberNoFilter by numeric project ID

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
countNo
errorNoHuman-readable error message
facetsNoDistribution counts when include_facets is true
detailsNoAdditional error context
entriesNo
successNo
categoryNoError category (validation, query, connection, internal)
degradedNoTrue if the search degraded to a slower fallback method due to infrastructure failure
highlightsNoFTS5 search snippets when include_highlights is true
searchModeNo
suggestionNoSuggested fix for the error
next_cursorNoCursor for the next page of results
recoverableNoWhether the error is recoverable
suggestionsNoFuzzy matches when fuzzy_match=true and no exact results were found
correctedQueryNoThe corrected query when auto_correct=true and a confident match was found
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv9.1.0
    • addedInput schema / properties / projectNumber
      Added value: +{
      +  "description": "Project number alias",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedInput schema / properties / project_number
      Added value: +{
      +  "description": "Filter by numeric project ID",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace identifier alias",
      +  "type": "string"
      +}
    • addedInput schema / properties / workspace_id
      Added value: +{
      +  "description": "Filter by workspace ID, or \"*\" for all workspaces",
      +  "type": "string"
      +}
  2. First observedv9.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds real value by clarifying these are 'soft-deleted' (recoverable, not purged) and only 'recently' deleted, but it leaves the retention window undefined and says nothing about pagination or ordering behavior.

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?

A single short, front-loaded sentence with no filler or repetition. It is efficient, but the terseness is arguably under-specification for a seven-parameter tool rather than true economy.

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

Completeness2/5

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

With seven optional parameters, ambiguous alias duplicates, and no required fields, an agent needs more than one sentence to call this correctly. An output schema exists so return values need not be described, but the retention window, default scoping (all workspaces vs one) and alias precedence are all missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Seven parameters at 57% schema coverage, and the description contributes nothing about any of them. In particular the schema exposes confusing duplicate alias pairs (workspaceId vs workspace_id, projectNumber vs project_number) plus use_test_db, limit and offset, and the description gives no guidance on which alias to use or how the '*' workspace value behaves.

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?

Names a specific verb (List) and a specific resource (soft-deleted entries) with two useful qualifiers: 'recently' and 'that can be restored'. An agent can tell this is a read of recoverable items rather than a permanent-delete listing, though the description never distinguishes it from the near-identical sibling 'team_list_deleted_entries'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no when-not-to-use, and no named alternative among the many siblings (restore_entry, team_list_deleted_entries, delete_entry). The phrase 'that can be restored' only faintly implies the follow-up workflow with restore_entry, leaving routing to inference.

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

Deploy Server

Other Tools