Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Create Connect Link

create_connect_link

Create a shareable link clients open to connect their social accounts to your workspace without an AdaptlyPost login. Control platforms, account limits, visibility, and expiry.

Instructions

Create a link someone else, such as a client, opens to connect their social accounts to this workspace without an AdaptlyPost login. With no options it is a quick link: it lasts 7 days, offers every platform, shows the client every account in the workspace and connects any number of accounts. visibility PRIVATE shows the client only the accounts they connected through the link; allowedPlatforms limits the platforms offered; maxAccounts makes the link stop working once that many accounts are connected through it; expiresAt or neverExpires changes when it stops working; returnUrl sends the client back to your app afterwards. Returns the url to send, plus startUrls, one per platform that connects through the network's own consent screen, for your own connect buttons. Connected accounts then show up in list_accounts. Revoke it with revoke_connect_link. Needs the accounts.manage permission, which Admin holds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLabel shown in the dashboard list of links
expiresAtNoWhen the link stops working, as an ISO 8601 date-time with a Z or ±hh:mm offset (e.g. "2026-11-30T23:59:59Z"). At least 1 hour and at most 365 days from now. Defaults to 7 days from now. Leave it out when neverExpires is true
returnUrlNoWhere the client goes after connecting, picking pages or channels, or being refused, so they come back to your app instead of staying on the link page. Must be https (http only for localhost) and carry no credentials. Your own query parameters are kept. The client arrives with status (connected or error), platform when known, one accountId per account connected (the id list_accounts shows), and on an error, error (a code) and message. A wrong Bluesky or WordPress password keeps the client on the link page
visibilityNoPRIVATE shows the client only the accounts they connected through this link. Defaults to PUBLIC
maxAccountsNoAccounts the link can connect in total. Reconnecting an account it already connected does not count again
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another
neverExpiresNotrue keeps the link working until it is revoked or reaches maxAccounts. Cannot be combined with expiresAt
allowedPlatformsNoPlatforms the client can pick. Omit or send [] for every platform

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with url (the link to send), token (pass it to revoke_connect_link), expiresAt (null when it never expires), name, visibility, allowedPlatforms, maxAccounts, returnUrl (null when not set) and startUrls: [{ platform, url }], one per platform the link offers that connects through the network's own consent screen. Bluesky and Telegram are left out because they connect on the link page. Add server= to the Mastodon URL, site= to the WordPress URL, and via=facebook to the Instagram URL to connect through a Facebook Page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare write/non-destructive/non-idempotent; the description layers on the behavior that actually matters: default 7-day expiry, PUBLIC vs PRIVATE visibility semantics, how maxAccounts counts reconnects, that neverExpires overrides expiresAt, the required accounts.manage permission, and the revocation path. It also discloses the non-obvious side effect that connected accounts appear in list_accounts, and the returnUrl error behavior for Bluesky/WordPress failures.

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?

Core purpose is front-loaded and every sentence carries information; there is no filler. It is dense, though, with long semicolon-chained clauses that are harder to scan than a short bulleted option summary, and a few lines duplicate the parameter descriptions verbatim.

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 an 8-parameter, all-optional creation tool with an output schema present, the definition covers defaults, permission requirements, follow-up tools, and revocation. Return values (url, startUrls) are described only as routing guidance rather than duplicating the output schema, which is the right division of labor.

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 the schema already carries per-parameter meaning and the baseline is 3. The description still adds synthesis the schema lacks: that omitting every option yields a coherent "quick link" profile, and that maxAccounts counting treats reconnects as free. The rest (visibility, allowedPlatforms, expiresAt/neverExpires) largely restates 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?

The description opens with a concrete verb and resource ("Create a link someone else...opens to connect their social accounts") and immediately scopes it against the sibling: revoke happens via revoke_connect_link, and results surface in list_accounts. An agent can distinguish this from revoke_connect_link and the account-listing tools without opening any schema.

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 gives clear context for the default case ("With no options it is a quick link: 7 days, every platform...") and names the correct alternative for undoing the action (revoke_connect_link). What's missing is explicit when-not guidance, e.g. when a client should instead be added as a user rather than connected via link, or how this compares with any direct connect flow.

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

Deploy Server

Other Tools