Skip to main content
Glama

Create a connect link for a client

clipember_create_client_connect_link

Create a link the user sends to their client so the client connects their OWN TikTok, YouTube or Instagram account by signing in on that network — no ClipEmber account or password sharing needed. The connected account joins the user's accounts (their plan's account limit applies) inside this client. Each network on the link can be connected once; the link stops working once all its networks are connected, when it expires, or when revoked. The URL is shown only in this result — pass it to the user as is.

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": {
      "clientId": "<clientId>",
      "platforms": "<platforms>"
    },
    "name": "clipember_create_client_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYesClient from clipember_list_clients
platformsYesNetworks the client may connect
senderNameNoName the client sees as the sender (person or agency, never an email); defaults to the user's profile name
expiresInDaysNoDays until the link expires (default 7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only say it is a non-read-only, non-destructive, non-idempotent, non-open-world write), the description discloses the key operational traits: one connection per network, the link dies when all networks are connected or when it expires or is revoked, the user's plan account limit applies, and the URL is returned only in this result and must be passed through as is. The one-time visibility of the URL is exactly the kind of detail an agent would otherwise get wrong.

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?

Three sentences, front-loaded with the purpose, then lifecycle constraints, then the critical output-handling instruction last. Nothing is padded; the em-dash clause in sentence one earns its place by pre-empting the password-sharing misconception.

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 carries the return-value burden and does so by stating that the URL appears only in this result and should be passed to the user verbatim. Combined with the lifecycle and account-limit details, an agent has everything needed to call this correctly and handle the response.

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 real meaning: 'each network on the link can be connected once' constrains how the platforms array behaves over the link's lifetime, and the note that connected accounts count against the plan's account limit informs why the platform set matters. It does not elaborate on senderName or expiresInDays beyond the schema, which keeps it at 4 rather than 5.

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 gives a specific verb and resource ('Create a link the user sends to their client') and immediately explains the mechanism: the client signs in on their own network, with no ClipEmber account or password sharing. That framing distinguishes it in spirit from the account-linking and preview-link siblings, so an agent knows this is the client-facing onboarding link, not a post/preview tool.

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?

Usage context is clear: this is what the user sends to a client so the client connects their own accounts. It also states the failure conditions (all networks connected, expiration, revocation), which helps an agent decide when to mint a fresh link. It stops short of naming alternatives such as the revoke or list connect-link tools, or the preview link tool, so the when-not guidance is implied rather than explicit.

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