Sliq

Get Tool Connect Url

get_tool_connect_url

Read-only

If the user says a service is already connected, call get_integration_status first — the service may already be active and need no link.

A link that opens fine but whose connection then fails is not a link problem — a fresh link routes to the same connect flow and fails the same way. Mint one fresh link and have the user retry once; if it still doesn't connect, the connection is stuck (not a link issue) — call escalate_to_team with the integration and what the user tried rather than re-minting again.

For linkedin, gmail, and outlook the return also includes data_backfill — a sentence stating how far back Sliq syncs history once connected. Relay it with the link so the user knows older data won't appear and how to request a longer backfill; when sharing several connect links in one message, merge the notes into a single short disclaimer instead of repeating one per link. Dict with the connect URL, integration name, the data_backfill note (linkedin/gmail/outlook), and connect_note (linkedin)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`on_behalf_of`	No	An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
`integration_id`	Yes	one of 'gmail', 'outlook', 'linkedin', 'slack', 'hubspot_mcp', 'attio', 'clarify', 'salesforce', 'notion', 'linear', 'fathom', 'granola', 'grain', 'zoom', 'otter', 'fireflies', 'circleback', 'superhuman', 'github', 'asana_mcp', 'atlassian_mcp', 'googledrive', 'googledocs', 'googlesheets', 'reddit', 'exa_websets', 'apollo'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / on_behalf_of

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / integration_id / description

Previous value: -"one of 'gmail', 'outlook', 'linkedin', 'slack', 'hubspot_mcp', 'attio', 'clarify',\n'salesforce', 'notion', 'linear', 'fathom', 'granola', 'grain', 'zoom',\n'otter', 'fireflies', 'circleback', 'superhuman', 'github', 'asana_mcp', 'atlassian_mcp',\n'calendly', 'googledrive', 'googledocs', 'googlesheets', 'reddit',\n'exa_websets', 'apollo'"New value: +"one of 'gmail', 'outlook', 'linkedin', 'slack', 'hubspot_mcp', 'attio', 'clarify',\n'salesforce', 'notion', 'linear', 'fathom', 'granola', 'grain', 'zoom',\n'otter', 'fireflies', 'circleback', 'superhuman', 'github', 'asana_mcp', 'atlassian_mcp',\n'googledrive', 'googledocs', 'googlesheets', 'reddit',\n'exa_websets', 'apollo'"

First observedSep 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries the behavioral burden and does so richly: it explains that a fresh link routes to the same connect flow (so a broken connection is not a link problem), prescribes the escalation path, and documents the data_backfill/connect_note fields returned for specific integrations.

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 core action, then justification, then troubleshooting. It is long, and the multi-clause sentence about a link that opens but fails to connect is dense, but nearly every sentence carries actionable routing or output guidance, so little is wasted.

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?

With no output schema, the description compensates by summarizing the return dict and the integration-specific note fields. Combined with clear escalation guidance and the caller-identity semantics covered by the schema, an agent has everything needed to call and use this tool.

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 description coverage is 100% and both parameters (integration_id with its full enum list, on_behalf_of) are documented in the schema. The description adds no parameter-level detail beyond what the schema already provides, so baseline 3 applies.

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?

The first sentence states a specific verb and resource: generate a clickable URL to connect a tool. It is immediately distinguishable from siblings like get_integration_status (which checks state) or escalate_to_team (which is named as the fallback path).

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?

Explicit when-to-use routing: if the user claims the service is already connected, call get_integration_status first. It also gives a clear when-not-to-repeat rule (mint one fresh link, retry once, then escalate rather than re-minting) and names the alternative tool.

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

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

Resources

Need Help?