Skip to main content
Glama

commsharbor

Commsharbor email google disconnect

commsharbor_email_google_disconnect

Remove this product's saved Google connection and pending consent. Existing email and service resources remain intact. Requires the owner's account session; an organization key cannot authorize Google access. Requires an account session in this organization. Reads site metadata only. Google access and refresh tokens remain encrypted on the server. This does not change DNS, buy a subscription or grant another product access to Google data.

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": {
      "organization_id": "<organization_id>",
      "service": "<service>"
    },
    "name": "commsharbor_email_google_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYessearch_console or analytics. Each connection has its own consent.
organization_idYesOrganization ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavioral context beyond the annotations: it says existing email and service resources remain intact, tokens stay encrypted, and the call does not change DNS, buy a subscription, or grant another product access. It also clarifies the account-session authorization constraint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the authorization requirement is repeated across two consecutive sentences and the negative-scope list is somewhat lengthy. It is informative but not maximally tight.

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?

For a two-parameter disconnect operation with no output schema, the description covers effects, non-effects, authorization, and resource persistence. An agent has enough information to call it correctly and understand the boundaries.

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 100%, so both organization_id and service are already documented in the schema. The description does not add service-specific meaning, such as explaining that search_console and analytics have separate consents, so it remains at the baseline.

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?

States a specific verb and resource: removing this product's saved Google connection and pending consent. It clearly distinguishes the action from connect/resolve siblings in the same Google email family.

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 use case is implied by 'Remove...' and authorization prerequisites are stated, including that an organization key cannot authorize Google access. However, it does not explicitly compare against alternatives such as reconnecting or resolving an existing connection, so the routing guidance is only moderate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.