Skip to main content
Glama

List connected social accounts

clipember_list_platform_connections
Read-onlyIdempotent

Show the user's connected accounts on TikTok, YouTube Shorts, Instagram Reels, LinkedIn and Bluesky — there can be several per platform, each with an id (connectionId). Pass that connectionId in clipember_create_post targets when a platform has more than one connected account. Also shows accounts that need reconnecting and the plan's account limit (accounts over it after a downgrade are locked), and which client (brand) each account belongs to — see clipember_list_clients. Connecting/disconnecting happens in the dashboard (https://clipember.com/connections), not via chat.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the baseline bar is lower; the description still adds real context by disclosing that accounts needing reconnection are surfaced, that plan account limits apply, that over-limit accounts are locked after a downgrade, and that brand/client attribution is included. It does not describe pagination or ordering, which keeps it just short of a 5.

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

Conciseness4/5

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

The core action and the connectionId hand-off are front-loaded, and every clause (reconnect state, plan limit, client attribution, dashboard link) carries distinct information. The single long paragraph with em-dash clauses is dense and could be broken up, but there is no filler.

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 has to explain what comes back, and it does: per-platform account lists, connectionId, reconnect-needed status, plan limit and locked accounts, and owning client. For a zero-parameter list tool, an agent has everything needed to call it and interpret the result.

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?

The tool takes zero parameters, which establishes a baseline of 4. The description instead spends its words explaining the meaning of a returned field (connectionId) and how it feeds another tool, which is useful orientation rather than required parameter documentation.

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 ("Show the user's connected accounts") and enumerates the supported platforms, so the agent knows exactly what is returned. It also distinguishes this tool from clipember_create_post and clipember_list_clients by explaining the relationship between them.

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 gives an explicit downstream use case — pass connectionId into clipember_create_post targets when a platform has multiple accounts — and an explicit exclusion: connecting/disconnecting happens in the dashboard, not via chat. That is when-to-use, how-to-use, and when-not-to-use in one place.

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