mcp-google-workspace

Overview Schema Source Related Servers Discussions Admin

Disconnect Google Workspace

disconnect_google_workspace

DestructiveIdempotent

Revokes the calling user's Google account grant and deletes their stored credentials, leaving other users' connections untouched. Prompts for confirmation before disconnecting.

Instructions

Disconnect the calling user's Google account: revoke the grant at Google and delete this user's stored credentials; other users' connections are untouched. The user is asked to confirm first, and the call returns status 'cancelled' if declined. Returns status 'disconnected' with grant_revoked and revocation_error; the stored credentials are deleted even when revocation fails. Reconnect later with connect_google_workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "disconnect_google_workspace"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`status`	No	Machine-readable operation status.
`grant_revoked`	No
`revocation_error`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.1.0Nov 6, 2026

removedInput schema / maxProperties
```
Removed value: -10000
```

removedInput schema / properties / confirm

Removed value: -{
-  "default": false,
-  "description": "Whether to enable confirm.",
-  "type": "boolean"
-}

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

removedOutput schema / description

Removed value: -"Structured response returned by this MCP tool."

removedOutput schema / properties / action

Removed value: -{
-  "description": "Response field: action.",
-  "type": "string"
-}

removedOutput schema / properties / grant_revoked / description
```
Removed value: -"Response field: grant revoked."
```

removedOutput schema / properties / resource

Removed value: -{
-  "additionalProperties": false,
-  "description": "Stable cross-tool Workspace resource handle when applicable.",
-  "properties": {
-    "etag": {
-      "description": "Provider entity tag.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "id": {
-      "description": "Provider resource identifier.",
-      "type": "string"
-    },
-    "kind": {
-      "description": "Workspace resource kind.",
-      "type": "string"
-    },
-    "mime_type": {
-      "description": "MIME type when applicable.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "modified_at": {
-      "description": "Last modification time.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "description": "Human-readable name.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "uri": {
-      "description": "Stable Workspace resource URI.",
-      "type": "string"
-    },
-    "web_url": {
-      "description": "Provider web URL.",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "kind",
-    "id",
-    "uri"
-  ],
-  "type": "object"
-}

removedOutput schema / properties / revocation_error / description
```
Removed value: -"Response field: revocation error."
```

removedOutput schema / title

Removed value: -"Disconnect Google Workspace Tool response"

First observedv0.3.7Jul 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description explains exactly what is destroyed: the Google grant is revoked and the calling user's stored credentials are deleted. It also discloses the confirmation flow, cancellation behavior, return statuses, and the important edge case that credentials are deleted even when revocation fails.

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?

The description is front-loaded with the main action and scope, then adds confirmation, return, failure, and reconnection details. It is somewhat dense but every sentence adds operationally relevant information for a destructive tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that annotations already mark the operation destructive and the output schema exists, the description still provides the critical behavioral details an agent needs: confirmation, cancellation, statuses, failure handling, and reconnection guidance. Nothing essential for safe invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is no parameter semantics burden beyond confirming the implicit target. The description correctly makes clear that the target is the calling user's Google account, not an arbitrary user or workspace.

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 states a specific verb and resource: disconnect the calling user's Google account by revoking the Google grant and deleting that user's stored credentials. It also clearly scopes the effect to the calling user by noting that other users' connections are untouched.

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 gives clear usage context, including that the user must confirm first and that declining returns 'cancelled'. It also routes the agent to connect_google_workspace for reconnection, though it does not explicitly enumerate when not to use this tool beyond the per-user scope.

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

Deploy Server