AEO Copilot MCP Server

list_deleted_prompts

Find recently deleted brand prompts still restorable within a 48-hour grace period. Review deletion batches, sample texts, and expiry times, then use the batchId to undo a deletion.

Instructions

List recently deleted prompts for a brand that are still restorable (48-hour grace window), grouped by delete batch with sample texts and expiry. Use the batchId with restore_prompts to undo a deletion.

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": {
      "brandId": "<brandId>"
    },
    "name": "list_deleted_prompts"
  }
}

Input Schema

Name	Required	Description	Default
`brandId`	Yes	The brand UUID from list_brands

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals meaningful behavior: the 48-hour grace window, grouping by delete batch, and included output fields (sample texts, expiry). It stops short of stating auth requirements or potential side effects, but 'list' clearly signals a read operation, making the gap minor.

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?

Two sentences with no filler. The first sentence front-loads the core purpose and key behavioral constraints; the second provides actionable cross-tool integration. Every clause earns its place.

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?

For a one-parameter list tool with no output schema and no annotations, the description is remarkably complete. It covers the operation, the scope condition (deleted, restorable, 48h), the output grouping and included data, and the follow-up action (restore_prompts with batchId). An agent has enough context to invoke it correctly and interpret results.

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 parameter brandId is already documented as 'The brand UUID from list_brands'. The tool description adds context by indicating the brand scope, but it does not add new parameter-level semantics beyond what the schema already provides, so the baseline of 3 applies.

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 states a specific verb ('list'), resource ('recently deleted prompts for a brand'), and a clear distinguishing scope ('still restorable (48-hour grace window)'). It also mentions grouping by delete batch, which further differentiates it from sibling tools like list_prompts and delete_prompts.

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

Usage Guidelines5/5

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

The description clearly indicates when to use this tool: when listing restorable deleted prompts within the 48-hour grace window. It also names the downstream tool, restore_prompts, and ties it to the batchId, giving explicit guidance on how the output feeds into the undo flow.

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