Skip to main content
Glama

commsharbor

Commsharbor email google connect

commsharbor_email_google_connect

Start five-minute Google consent with PKCE. Return an authorization URL. Signing in does not grant this access. 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_connect"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: a five-minute consent window, PKCE, the fact that tokens are encrypted server-side, and an explicit negative scope ('does not change DNS, buy a subscription or grant another product access to Google data'). It does not say what happens if the window expires or how the consent is later polled, but the safety profile is well covered and the annotations already declare non-readOnly/non-idempotent.

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?

Short, front-loaded sentences with the key action and return value first. Slight redundancy between 'Requires the owner's account session; an organization key cannot authorize Google access' and 'Requires an account session in this organization'.

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?

No output schema exists, and the description supplies the return value (authorization URL), the consent lifetime, and the auth requirements. It stops short of describing the next step in the flow (presumably google_resolve) and any failure/expiry behavior.

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% and both enums are described in the schema ('Each connection has its own consent', 'Consent return language'). The description adds no parameter-level detail, so baseline 3 applies.

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?

States a specific verb and resource ('Start five-minute Google consent with PKCE') and the return value ('Return an authorization URL'). It does not name a sibling to differentiate from (google_resolve, google_disconnect), but the connect/resolve/disconnect naming plus the service enum makes the scope clear enough.

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?

Gives prerequisites (owner's account session, organization key cannot authorize, signing in alone doesn't grant access) but never says when to pick this tool over google_resolve or google_disconnect, nor what to do after obtaining the URL. Usage is implied by the verbs, not routed.

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.