Skip to main content
Glama

Create a client connect link

create_connect_link

A link to send the account owner (your client or your human). They open it, sign in to the network and pick their accounts — no Shager account needed. The accounts then appear in list_channels. Live: YouTube channels, X (Twitter) accounts, LinkedIn personal profiles, TikTok accounts, Bluesky accounts, Telegram channels, Mastodon accounts, Pinterest business accounts and Tumblr blogs. Facebook: Awaiting Meta's approval: until then, only people we gave early access can connect. Pages are published automatically. Facebook lets no app publish to personal profiles, so for a profile Shager gets the post ready at its time and emails you a link: one tap shares it from your phone, a few short steps from a computer. Nothing goes on the profile until you share it. On a profile Facebook picks the video's thumbnail itself, so your cover image waits on that page for you to upload by hand. A profile gets no first comment and no numbers. That works today, without waiting for Meta. Posts, photos, video, Reels and Stories, with your own cover image for videos. First comment with a clickable link. Instagram: Awaiting Meta's approval: until then, only people we gave early access can connect. Connected directly with Instagram Login or through a Facebook Page. Your own cover image for Reels. Links in captions and comments aren't clickable on Instagram: the tracked link goes in the first comment as text, and a clickable link can only go in the profile. Threads: Awaiting Meta's approval: until then, only people we gave early access can connect. Up to 500 characters (an emoji counts as several). Text, up to 20 images and videos in one carousel, or a video up to 5 minutes. Text posts can carry a link card, and any post can get a topic and a choice of who can reply. The first comment is posted as a reply, and replies, views and likes show up in Shager. You sign in on Threads' own screen and never give us your password. Google Business Profile: Awaiting Google's approval: until then, only people we gave early access can connect. Each location is its own profile, and you choose which locations to connect. A post is an update, an event or an offer, with up to 1,500 characters, one photo and a button such as Book, Order or Learn more. No video and no first comment. Reviews can be read and answered in Shager, by hand only, when you decide. Profile views, calls, website clicks and direction requests show up in Shager. You sign in on Google's own screen and never give us your password. (Not available in an unclaimed sandbox.)

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "create_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoWho the link is for (shown to the agency only).
workspace_idYesWorkspace id from list_workspaces
idempotency_keyNoAny unique string you choose (REST: the Idempotency-Key header works too). Retrying with the same key and body returns the first result instead of creating a second one. Kept 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-open-world, non-idempotent creation. The description adds genuine context beyond them: the recipient needs no Shager account, they sign in on the network's own screen, and the link is for the 'account owner (your client or your human)'. However, it omits the practically important traits for an invite link — expiry, single-use behavior, who may redeem it, and whether revoke_connect_link invalidates it — while spending most words on publishing capabilities after connection.

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

Conciseness2/5

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

The essential sentence is front-loaded, but the bulk of the text is a long platform-by-platform publishing reference (Facebook profile workarounds, Instagram caption link rules, Threads character counts, Google Business Profile post types) that has little bearing on creating a connect link. That volume buries the actionable information and is not appropriate for a three-parameter creation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple creation tool with one required parameter and no output schema, the description should cover link lifecycle and routing to list_connect_links or revoke_connect_link. Instead it is complete about what platforms publishing supports after connection and incomplete about the link itself — validity, delivery, redemption constraints, and cleanup.

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 label, workspace_id, and idempotency_key are already fully documented in the schema. The description adds nothing about the label's audience, workspace scoping, or idempotency semantics, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line conveys that this produces a link sent to an account owner who then signs in and selects accounts, so the artifact is identifiable. But it never states a verb like 'creates' and never distinguishes it from siblings such as create_link, list_connect_links, or revoke_connect_link. An agent must infer the action from the title rather than the description.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no precondition, and no alternative named. The only routing hint is 'The accounts then appear in list_channels', which is a downstream consequence, not a selection rule. Nothing says when to use this versus create_link or when a connect link is the wrong choice.

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.

Resources