Skip to main content
Glama
Sign In
AI Site Manager MCP

AI Site Manager MCP

by nkd3v
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

aism_migration_rollback

Destructive

Undo a migration by deleting content it created, restoring changed site settings, clearing its ID map, and preserving pre-existing target content.

Instructions

Undo a migration on the target: permanently delete posts, media files, terms, comments and user accounts the migration created (their remaining content goes to the key owner), restore site settings it changed, and forget its ID map. Objects matched to pre-existing target content are kept. Requires migration:delete on the target.

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": {
      "target": "<target>"
    },
    "name": "aism_migration_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoConfigured source site name, used to look up its UUID.
targetYesConfigured site name the migration went into.
max_secondsNo
source_uuidNoSource site_uuid, for when the source is no longer configured (see aism_migration_manifest on the target: imported_sources).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds far more: exactly which entities are deleted, that orphaned content transfers to the key owner, that settings are restored and the ID map discarded, and that matched objects survive. This is rich operational context that goes well beyond the annotation flags.

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 dense sentence is front-loaded with the destructive action, and each clause adds concrete scope information. It is long but essentially every phrase earns its place; only the trailing permission note is somewhat boilerplate.

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 destructive, no-output-schema mutation tool, the description covers what is destroyed, side effects on settings and content ownership, and the auth requirement. The only minor gap is the meaning/behavior of max_seconds, which is left entirely to the schema.

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 75%, and the description adds little parameter-level detail beyond the schema. It references the manifest for recovering a source UUID, which merely echoes the source_uuid schema description, and never explains max_seconds or the source/target interaction directly.

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+resource ('Undo a migration on the target') and enumerates exactly what is removed, restored, and forgotten. It is clearly distinguishable from siblings like aism_migration_run, aism_migration_copy, and aism_migration_plan without opening any 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 establishes the use case (reversing a completed migration) and the key scoping rule that objects matched to pre-existing content are preserved, plus the auth prerequisite (migration:delete). It stops short of naming an explicit alternative or stating when rollback should not be used.

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