Skip to main content
Glama

List connected Facebook and Instagram accounts

klynx_list_social_accounts
Read-onlyIdempotent

Use this when the user wants to publish or schedule a post, or asks which Facebook Pages or Instagram accounts are connected to Klynx. Returns each connected account with its account_id, platform (facebook or instagram), name, status (active or needs_reconnecting) and whether it can publish, plus the Social Connections link. Free, takes no inputs and changes nothing. If nothing is connected, call klynx_get_connect_link.

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_list_social_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYes
accountsYes
next_stepYes
connect_urlYesThe Social Connections page, where the owner connects accounts in a browser.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: it costs nothing, takes no inputs, and returns status values including 'needs_reconnecting' and a publishability flag, which tells the agent how to interpret results rather than just that the call is safe.

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?

The triggering condition is front-loaded, followed by return shape, cost/side-effect reassurance, and the fallback branch. Four dense sentences with no filler, each carrying distinct decision-relevant information.

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 a zero-parameter read tool with full annotation coverage and an output schema, the description covers everything an agent needs: when to call it, what comes back in prose terms, that it is free and side-effect-free, and what to do when the result is empty. Nothing material 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?

There are zero parameters, which sets the baseline at 4, and the description reinforces this by stating it takes no inputs. No additional parameter meaning is possible here, so the score reflects the baseline rather than any added semantic detail.

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 specific verb and resource: listing connected Facebook Pages and Instagram accounts, with explicit triggering intents (publishing/scheduling a post or asking which accounts are connected). An agent can distinguish this from siblings like klynx_get_connect_link or klynx_publish_now 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 Guidelines5/5

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

It states exactly when to use the tool (before publishing/scheduling, or when the user asks what is connected) and gives an explicit edge-case branch: if nothing is connected, call klynx_get_connect_link. That is a named alternative plus the condition that selects it, leaving nothing to inference.

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