AdaptlyPost

Create Connect Link

create_connect_link

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. Returns the url to send. Connected accounts then show up in list_accounts. Revoke it with revoke_connect_link. Needs the accounts.manage permission, which Admin holds.

Input Schema

Name	Required	Description
`name`	No	Label shown in the dashboard list of links (max 80 characters)
`expiresAt`	No	When 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
`visibility`	No	PRIVATE shows the client only the accounts they connected through this link. Defaults to PUBLIC
`maxAccounts`	No	Accounts the link can connect in total. Reconnecting an account it already connected does not count again
`workspaceId`	No	Workspace 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
`neverExpires`	No	true keeps the link working until it is revoked or reaches maxAccounts. Cannot be combined with expiresAt
`allowedPlatforms`	No	Platforms the client can pick. Omit or send [] for every platform

Output Schema

Name	Required	Description	Default
`result`	No	An object with url (the link to send), token (pass it to revoke_connect_link), expiresAt (null when it never expires), name, visibility, allowedPlatforms and maxAccounts.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: 7-day default lifetime, 1-hour-to-365-day bounds, that connected accounts surface in list_accounts, the returned url, and the required accounts.manage permission (and that Admin holds it). These are exactly the operational facts an agent needs before calling a non-destructive write.

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?

Front-loads the purpose, then packs the default behavior and each option into a tight sequence of sentences. No filler and no repetition of schema-only details.

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?

Output schema covers return values, and the description still states it returns the url. With annotations covering safety and the description covering lifetime, permissions, and follow-up tools, an agent has everything needed to call it correctly.

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 baseline is 3, but the description adds behavioral meaning: PRIVATE limits what the client sees, allowedPlatforms limits what is offered, and maxAccounts makes the link stop working after that many connections. That is useful semantics layered over the schema.

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 connect link) plus the exact scenario: a client connecting social accounts without an AdaptlyPost login. It also names the related tools (list_accounts, revoke_connect_link), so an agent can distinguish it from unrelated create_* 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?

Explains the no-option default case and what each option changes, and points to revoke_connect_link for teardown. It stops short of explicitly saying when to use a different tool for connecting accounts, but the context is otherwise clear.

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

All AdaptlyPost 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?