Skip to main content
Glama

List deleted reviews (Ledger)

list_deleted_reviews
Read-only

Reviews Prisma found removed from their platform during one month, with the copy it kept (text, author, stars), when it first and last saw each one, and whether it left in a mass removal. Evidence to show a client or to back a claim to the platform; Prisma can’t restore reviews.

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_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoThe month, YYYY-MM (UTC). Default: the current month.
platformNo
location_idNoOnly this location (from list_locations).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds context the annotations cannot: that the data is a retained copy of content removed elsewhere, that detection is time-bounded to a month, and critically that 'Prisma can't restore reviews' — a limitation an agent might otherwise assume away. It stops short of describing result volume or pagination.

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?

Purpose is front-loaded in the first clause, and every subsequent element — returned fields, timestamp semantics, mass-removal flag, evidence use case, restore limitation — carries information an agent needs. Two sentences, no filler or repetition of the tool name.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly, and it flags the restore limitation. What is missing for a list-style tool is result-size behavior (limits, pagination, ordering) and the default scope when platform/location_id are omitted.

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 67%: month documents its YYYY-MM pattern and default, location_id points at list_locations, and platform is a self-describing enum. The description only reinforces the month scoping ('during one month') and says nothing about platform filtering or what happens when location_id is omitted, so it adds little beyond the schema. Baseline 3 is appropriate at this coverage level.

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 opens with a specific verb and resource ('Reviews Prisma found removed from their platform') and scopes it to one month. It then enumerates exactly what comes back (kept copy with text, author, stars, first/last seen timestamps, mass-removal flag), which cleanly separates it from list_reviews in an agent's mind without needing to open the schema.

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?

It gives a concrete use case — 'Evidence to show a client or to back a claim to the platform' — which tells the agent when this tool is the right pick. It does not name an alternative or state exclusions (e.g. when to use list_reviews instead), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources