Skip to main content
Glama

Get the link to connect Facebook or Instagram

klynx_get_connect_link
Read-onlyIdempotent

Use this when the user needs to connect, or reconnect, a Facebook Page or Instagram business account to Klynx. Returns the link to the Social Connections page in the Klynx web app, where the owner connects Facebook and Instagram in a browser; then call klynx_list_social_accounts again. Free, takes no inputs and changes nothing. Facebook sign-in never happens in the chat: do not ask the user for Facebook or Instagram passwords or codes.

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": "klynx_get_connect_link"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
next_stepYes
platformsYes
connect_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds behavior not captured there: the tool is free, takes no inputs, changes nothing, and crucially that Facebook sign-in never occurs in-chat so credentials must not be requested. That authentication constraint is the key behavioral fact an agent needs and it is absent from structured fields.

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 usage trigger and the return value, followed by the sequential instruction and the safety prohibition. No sentence is redundant and the ordering matches how an agent would need to act.

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?

An output schema exists, so return-shape detail is unnecessary, and the description still clarifies what the link points to and where the user completes the flow. For a zero-parameter, read-only link generator, nothing an agent needs to call it correctly is missing.

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?

With zero parameters, the schema baseline applies, and the description only adds the confirmatory 'takes no inputs.' There is no parameter meaning to add here, so the modest score reflects the lack of opportunity rather than any deficiency.

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 names a specific verb and resource ('Returns the link to the Social Connections page in the Klynx web app') and constrains it to a specific purpose: connecting or reconnecting a Facebook Page or Instagram business account. An agent can immediately distinguish this from siblings like klynx_list_social_accounts or klynx_publish_now.

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?

It states exactly when to use it ('when the user needs to connect, or reconnect'), what to do afterward ('then call klynx_list_social_accounts again'), and what not to do ('do not ask the user for Facebook or Instagram passwords or codes'). The routing and follow-up sequence is fully 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