Skip to main content
Glama
Sign In

Socialync

by io.github.JackVitick
OverviewDiscussionsAdmin

list_connections

Read-only

List all connected social media platform accounts for a profile. Returns platform name, profile name, and connection status for each. A connection with requiresReconnect true cannot publish: its reason says why in plain words, and scheduled posts to it will fail until the user reconnects it in Socialync Settings. X connections also carry maxCaptionLength (280 free, 4000 with X Premium) and xPremium. Pass profileId to inspect a specific authorized profile; omit it to use the single/default authorized profile.

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

Input Schema

NameRequiredDescriptionDefault
profileIdNoThe Socialync profile whose connections to list. Call list_profiles to see authorized profiles. Omit to use the single/default authorized profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish that this is a safe read-only, non-destructive, closed-world operation. The description adds substantial behavioral context beyond annotations: return fields, requiresReconnect consequences, the reason field, scheduled-post failure behavior, and X-specific caption-length 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?

The description is front-loaded with the core purpose, then efficiently adds return shape, reconnect edge cases, X-specific fields, and parameter behavior. Each sentence carries useful information and 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?

There is no output schema, but the description explains the returned fields and the special X caption-length fields. It also explains the operational meaning of requiresReconnect and scheduled-post failures, giving an agent enough context to use and interpret the tool correctly.

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 description coverage is 100%, so the single optional profileId parameter and its default behavior are already documented in the schema. The description reinforces that same behavior but does not add syntax, format, or enum details beyond what the schema provides, making the baseline 3 appropriate.

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 first sentence gives a specific verb and resource: 'List all connected social media platform accounts for a profile.' It also distinguishes this from the sibling list_profiles by making clear that it inspects platform connections for a given profile, and it names the returned fields.

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?

The description gives clear usage context: pass profileId to inspect a specific authorized profile, or omit it to use the single/default authorized profile. It does not explicitly name alternatives or when-not conditions, so it is strong but not fully routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Socialync toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources