Skip to main content
Glama

commsharbor

Commsharbor email google resolve

commsharbor_email_google_resolve

Resolve website addresses for up to 20 selected Analytics properties. Search Console does not use this route. 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>",
      "properties": "<properties>"
    },
    "name": "commsharbor_email_google_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYessearch_console or analytics. Each connection has its own consent.
propertiesYesAuthorized properties/ID values from the catalog, at most 20 unique entries.
organization_idYesOrganization ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint=false and idempotentHint=false already declared, the description adds real value by disclosing the auth model (owner session required, org key insufficient) and the security posture (tokens stay encrypted server-side). The negative list ('does not change DNS, buy a subscription or grant another product access') bounds side effects. 'Reads site metadata only' sits in mild tension with readOnlyHint=false, but is plausibly explained by server-side token refresh rather than data mutation, so it does not rise to a contradiction.

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 core operation is front-loaded, which is good, but the middle is padded: 'Requires the owner's account session; an organization key cannot authorize Google access' and 'Requires an account session in this organization' say nearly the same thing twice. The trailing negative list is useful but adds bulk that could be compressed into one clause.

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 3-parameter tool with no output schema, the description covers what is read ('site metadata only'), what comes back in spirit (resolved website addresses), and the authorization constraints that gate success. The remaining gap is the ambiguous relationship between the described route and the search_console enum value, plus no note on partial failures when some of the 20 properties cannot be resolved.

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 the baseline is 3 and the schema already explains organization_id, service, and the 20-item unique property list. The description restates the 20-property cap but adds no syntax or format detail. Worse, 'Search Console does not use this route' conflicts with the service enum that explicitly accepts 'search_console', leaving the agent unsure whether that value is valid here.

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 opens with a concrete verb and resource: 'Resolve website addresses for up to 20 selected Analytics properties', which tells an agent exactly what the tool produces. It also carves out scope by saying 'Search Console does not use this route', distinguishing it from other Google-connection siblings. It never names a specific sibling tool (e.g. commsharbor_email_google_catalog), so differentiation is by scope rather than by routing.

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 states a clear exclusion ('Search Console does not use this route') and the authorization precondition ('Requires the owner's account session; an organization key cannot authorize Google access'). That is enough for an agent to decide whether it can call the tool at all. It stops short of saying when to prefer this over commsharbor_email_google_catalog or the connect/disconnect siblings.

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.