Revdoku

Bucket Unlock

bucket_unlock

Idempotent

Unlock a bucket locked by this MCP connector.

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.8/5.0

Behavior3/5

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

Annotations already declare the tool is a non-read-only, idempotent, and non-destructive mutation. The description adds the scope constraint 'locked by this MCP connector', which is useful, but provides no additional behavioral detail such as effects on access, failure handling, or reversibility. The description does not contradict the annotations.

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 a single clear sentence with no redundancy or filler. It is front-loaded with the primary action and object, making it immediately scannable and efficient for an agent.

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 simple unlock operation, the combination of the description, full parameter schema, and annotations covers the essential facts: what it does, that it is idempotent and non-destructive, and what parameters are needed. The description could mention how to verify a bucket is locked, but that is ancillary given the richness of the other structured signals.

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%, so the input schema fully documents both parameters. The tool description does not add any parameter-level meaning beyond what the schema already provides. Since the schema carries the full burden, 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'unlock' and the resource 'a bucket', with a specific scope ('locked by this MCP connector'). This immediately distinguishes it from sibling tools like bucket_unlock_file or bucket_lock, which target different resources or actions. Even without naming alternatives, an agent can identify what this tool does.

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 when to use the tool: when a bucket is locked by this MCP connector. However, it offers no explicit alternatives or when-not-to-use guidance, such as pointing to bucket_unlock_file for files or bucket_lock for locking. The usage context is present but not fully elaborated.

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.