AEO Copilot MCP Server

restore_prompts

Restore recently deleted prompts in bulk by providing the delete batch ID. Recover prompts within the 48-hour grace window to undo accidental deletions.

Instructions

Restore a batch of recently deleted prompts (undo a delete_prompts call). Works while the batch is still inside the 48-hour grace window; get the batchId from list_deleted_prompts or from the delete_prompts response.

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": {
      "batchId": "<batchId>"
    },
    "name": "restore_prompts"
  }
}

Input Schema

Name	Required	Description	Default
`batchId`	Yes	The delete batch UUID from list_deleted_prompts or delete_prompts

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the operation is batch-scoped, that it reverses a delete_prompts call, and that it is only valid within 48 hours. It doesn't cover edge cases such as already-restored batches or failure/return behavior, but the core side effects are clear.

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 short sentences: the first names the operation, the second provides the time constraint and ID source. Every clause is load-bearing; there is no filler or restatement.

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?

For a single-parameter restore operation, the description supplies the action, the exact batchId source, and the availability window, which is enough for an agent to select and invoke it correctly. Return-shape and failure-mode details are not described, but the low complexity and complete schema keep this from being a serious gap.

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% and the batchId description in the schema already states its origin ('from list_deleted_prompts or delete_prompts'). The tool description repeats this origin without adding new format, type, or validation nuance, so it stays at the baseline of 3.

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 ('restore') and a concrete resource ('a batch of recently deleted prompts'), and immediately anchors the operation to delete_prompts via 'undo a delete_prompts call'. This clearly differentiates it from the prompt-management siblings such as list_prompts, update_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 Guidelines4/5

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

It explicitly states the governing condition ('48-hour grace window') and tells the agent exactly where to obtain the required batchId (list_deleted_prompts or delete_prompts response). It lacks an explicit exclusion for batches outside the window, but the grace-window condition makes the usage boundary clear.

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