Revdoku

Bucket Unarchive

bucket_unarchive

Restore one archived bucket back to the active bucket list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bucket_id`	Yes	Revdoku bucket id returned by bucket_list or bucket_get, for example bkt_...
`account_id`	No	Optional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a bucket id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bucket`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 19, 2026

addedOutput schema / properties / bucket / properties / inbound_email

Added value: +{
+  "additionalProperties": false,
+  "description": "Accepted email activity. Creation and write-authorized include_inbound_email reads also return the full address and receiving state. Compare received_count for new mail, then read last_received_path + message.json. Not a delivery cursor.",
+  "properties": {
+    "address": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "blocked_reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "configured": {
+      "type": "boolean"
+    },
+    "enabled": {
+      "type": "boolean"
+    },
+    "last_received_at": {
+      "description": "Latest accepted message receipt time, in UTC. Null before any recorded delivery.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "last_received_path": {
+      "description": "Latest message folder relative to the bucket, ending in /. Null when unknown; manual moves/deletion can make it stale.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "max_file_size_bytes": {
+      "type": "integer"
+    },
+    "max_pdf_size_bytes": {
+      "type": "integer"
+    },
+    "monthly_limit": {
+      "type": "integer"
+    },
+    "ready": {
+      "type": "boolean"
+    },
+    "received_count": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "rotation": {
+      "properties": {
+        "monthly_limit": {
+          "type": "integer"
+        },
+        "remaining": {
+          "type": "integer"
+        },
+        "resets_at": {
+          "type": "string"
+        },
+        "used": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "received_count",
+    "last_received_at",
+    "last_received_path"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 8, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "Optional account id from revdoku_status.accounts for this call only. Omit for the credential's default account. Client accounts require explicit Agency authorization; never infer an account from a bucket id.",
+  "type": "string"
+}

Changed2 schema fields changedSep 3, 2026

changedOutput schema / properties / bucket / properties / search_engine_visibility / properties / locked_reason / enum

Previous value: -[
-  "anonymous_preview",
-  "temporary_preview",
-  "protected_access",
-  "account_policy",
-  null
-]New value: +[
+  "temporary_preview",
+  "protected_access",
+  "account_policy",
+  null
+]

changed

Output schema / properties / bucket / properties / website / properties / search_engine_visibility / properties / locked_reason / enum

Previous value: -[
-  "anonymous_preview",
-  "temporary_preview",
-  "protected_access",
-  "account_policy",
-  null
-]New value: +[
+  "temporary_preview",
+  "protected_access",
+  "account_policy",
+  null
+]

Changed3 schema fields changedAug 31, 2026

removedOutput schema / properties / bucket / properties / path_permissions

Removed value: -{
-  "items": {
-    "properties": {
-      "path": {
-        "type": "string"
-      },
-      "permission": {
-        "enum": [
-          "read_write",
-          "read_only"
-        ],
-        "type": "string"
-      },
-      "source": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / bucket / properties / wbuilder_contract

Removed value: -{
-  "additionalProperties": true,
-  "type": [
-    "object",
-    "null"
-  ]
-}

removedOutput schema / properties / bucket / properties / website_type

Removed value: -{
-  "enum": [
-    "static",
-    "wbuilder"
-  ],
-  "type": "string"
-}

Changed2 schema fields changedAug 18, 2026

addedOutput schema / properties / bucket / properties / search_engine_visibility

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "allow_search_indexing": {
+      "type": "boolean"
+    },
+    "locked": {
+      "type": "boolean"
+    },
+    "locked_reason": {
+      "enum": [
+        "anonymous_preview",
+        "temporary_preview",
+        "protected_access",
+        "account_policy",
+        null
+      ],
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "owner_preference": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "allow_search_indexing",
+    "owner_preference",
+    "locked"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / bucket / properties / website / properties / search_engine_visibility

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "allow_search_indexing": {
+      "type": "boolean"
+    },
+    "locked": {
+      "type": "boolean"
+    },
+    "locked_reason": {
+      "enum": [
+        "anonymous_preview",
+        "temporary_preview",
+        "protected_access",
+        "account_policy",
+        null
+      ],
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "owner_preference": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "allow_search_indexing",
+    "owner_preference",
+    "locked"
+  ],
+  "type": "object"
+}

First observedAug 17, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations indicate this is not read-only, not destructive, not idempotent, and not open‑world. The description doesn't contradict these, and it adds the key behavioral detail that it moves a bucket from archived to active state. However, it doesn't mention potential side effects, such as whether the action is reversible or if any data is affected.

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?

Single, clear sentence with no filler. The key verb and object are front-loaded, and it's appropriately concise for a simple operation.

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 straightforward restore operation, this is adequate. The output schema is present, so return values are covered. The schema covers parameters. The only missing element is explicit guidance on when this tool should be used compared to bucket_archive or when it might fail, but that is minor given the simplicity.

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?

The schema already provides full descriptions for both parameters (bucket_id with example format, account_id with usage and caution). The description adds no further parameter meaning beyond what the schema gives, so with 100% schema coverage, a baseline of 3 is appropriate.

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?

The description states a clear verb ('Restore') and resource ('archived bucket back to the active bucket list'), making the purpose unambiguous. It effectively distinguishes from sibling tools like bucket_archive and bucket_delete_permanently.

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

Usage Guidelines3/5

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

The description implies usage: it's for restoring archived buckets. However, it doesn't explicitly state when not to use it or mention alternative tools (e.g., bucket_archive for archiving). There's no guidance on prerequisites like bucket ownership or permissions.

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

All Revdoku tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.