Argorant

Connect Google Workspace mailboxes

argorant_connect_google_workspace

Connect Google Workspace mailboxes as sending mailboxes, without passwords and without signing in to each mailbox. Use it for Google Workspace; Microsoft 365 and other providers connect on the Mailboxes page or through Argorant's own mailbox form. It works in two steps. Called without emails, it returns the client ID and the permissions the Workspace admin pastes in Google Admin > Security > API controls > Domain-wide delegation; once that is done, the same call lists every mailbox and alias. Then call it again with emails, or an empty list for all of them, to connect those addresses. Nothing is sent. Afterwards argorant_list_inboxes shows them and argorant_set_campaign_senders adds them to a campaign. More in the docs at https://docs.argorant.com/docs/agents/tools#mailboxes

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": {
      "admin_email": "<admin_email>"
    },
    "name": "argorant_connect_google_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`emails`	No	The addresses to connect, from the list the first call returned. An empty list connects all of them. Leave it out on the first call.
`admin_email`	Yes	The Google Workspace admin's address.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description goes well beyond that by disclosing the domain-wide delegation prerequisite, the exact Google Admin navigation path for the admin, the two-step call protocol, and the reassurance that nothing is sent. That is precisely the external-setup and side-effect context an agent needs before making a mutating call.

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?

Front-loaded with the purpose and provider scoping, then the two-step flow, then next steps. It is somewhat long and the trailing doc URL plus the next-steps sentence are marginal, but every other sentence carries information an agent needs to sequence the calls correctly.

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 tool with an output schema and full schema coverage, the description covers the remaining gaps: prerequisites, call ordering, and what follows. Nothing needed to invoke it correctly is 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?

Schema coverage is 100%, so baseline is 3, but the description adds operational meaning the schema alone doesn't convey: omitting emails is the first-call mode, an empty list means all mailboxes, and the values come from the list the first call returned. Only the admin_email parameter is left to the schema, which handles it adequately.

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 (connect Google Workspace mailboxes as sending mailboxes) and immediately scopes it to one provider, explicitly excluding Microsoft 365 and other providers. The agent can distinguish it from argorant_connect_smtp_mailbox and the generic mailbox form without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use this for Google Workspace, use the Mailboxes page or Argorant's own mailbox form for Microsoft 365 and others. It also lays out the mandatory two-call sequence (first without emails to get client ID + permissions, then with emails to connect) and names the follow-up tools argorant_list_inboxes and argorant_set_campaign_senders.

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

All Argorant 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.