Skip to main content
Glama

integrations_connect_link

Create a one-time link that lets a person WITHOUT a DialogBrain account connect their own Google account to this workspace's Google integration (for example so the workspace can create files in that person's Google Drive). The person opens the link, reads who is asking, signs in with Google and the access is stored on the integration; the link then stops working. If a Google account is already connected, the new one replaces it. Returns url and expires_at (default 24 hours, at most 7 days). Send the link only to the person it is for. For a person's own client with the admin role; an agent cannot call it.

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": {
      "integration_id": "<integration_id>"
    },
    "name": "integrations_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
expires_inNoSeconds the link stays valid. Default 86400 (24 hours), maximum 604800 (7 days).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
integration_idYesThe Google integration's id (from integrations.list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations, which only declare a non-read-only, non-idempotent, non-destructive write. The description discloses that the link is single-use and stops working, that a new connection replaces an existing one (a consequential side effect not implied by destructiveHint=false), the 24h/7d expiry window, the return fields, and the privilege requirement.

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

Conciseness5/5

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

The core capability is front-loaded in the first sentence, followed by lifecycle, side effects, return values, and safety constraints in descending order of importance. No sentence is filler; the parenthetical example earns its space by anchoring the use case.

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 three-parameter, non-idempotent mutation with no output schema, the description supplies everything an agent needs: what it produces, what it returns, how long it lives, what it overwrites, and that an agent may not call it at all.

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 integration_id and expires_in are already self-documenting; the description's expiry details merely restate them. The only parameter with no added meaning anywhere is in_workspace, whose workspace-override semantics are left entirely to the schema text.

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 ('Create a one-time link') plus the exact mechanism: a person without a DialogBrain account connecting their own Google account to this workspace's Google integration. The parenthetical example (workspace creating files in that person's Drive) makes the outcome concrete and distinguishes it from generic auth-setting or channel-connect siblings.

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?

Gives clear caller context ('For a person's own client with the admin role; an agent cannot call it') and a distribution rule ('Send the link only to the person it is for'), which effectively tells an agent when it must not invoke this. It stops short of naming an alternative for connecting the workspace's own Google account (e.g. integrations_set_auth), leaving that inference to the agent.

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.