Revdoku

Bucket Archive

bucket_archive

Archive one bucket. Active websites must be unpublished first.

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 already indicate this is not read-only and not idempotent; the description adds a meaningful behavioral prerequisite about unpublishing active websites. It does not, however, disclose whether archiving is reversible, what happens to the bucket's contents, or any side effects on publication, which would be valuable given the destructiveHint is false but not explanatory.

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?

The description is two short sentences with no filler. The core action is stated first, and the key prerequisite follows, making it highly efficient and well-structured.

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 tool with two parameters, an output schema, and existing annotations, the description covers the main prerequisite and is mostly complete. It would be slightly better to mention that bucket_unarchive can reverse the action or clarify the archived state's visibility, but these are minor gaps given the modest complexity.

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%, with both bucket_id and account_id already described in the schema. The description adds no parameter-specific meaning beyond the schema, so the baseline score 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 specific action and resource: 'Archive one bucket.' This is clear and aligns with the tool name, but it does not explicitly contrast with related operations like bucket_delete_permanently or bucket_lock, leaving some ambiguity about what 'archive' entails relative to those siblings.

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 phrase 'Active websites must be unpublished first' provides a concrete precondition and implies the tool should be used only after unpublishing active sites. However, it does not name alternatives or specify when not to use this tool versus bucket_unarchive, bucket_delete_permanently, or bucket_lock, so guidance is implied rather than explicit.

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.