Skip to main content
Glama

List connected social accounts

autoshort_list_social_accounts
Read-onlyIdempotent

Lists connected publishing accounts across YouTube, TikTok, Facebook Page, Instagram, and Threads, showing usernames, reconnect needs, publish modes, AI-disclosure settings, and daily limits.

Instructions

List the connected publishing accounts per platform (YouTube, TikTok, Facebook Page, Instagram, Threads) with username, whether they need reconnecting, the publish mode, the AI-disclosure handling and today's platform limits. Never returns tokens. For a platform that is not connected, call autoshort_get_connection_status to get a one-click connectUrl. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds genuine context beyond them: 'Never returns tokens' (a security reassurance), 'Free' (no credit consumption), and an enumeration of what each row contains. No output schema exists, so it carries the return-shape burden and does so reasonably, though it does not describe ordering or behavior with zero connected accounts.

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?

Two sentences, both dense with information: the first front-loads what is returned and its fields, the second handles the non-connected case. No filler, no restatement of the title.

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 simple no-parameter read with annotations covering the safety profile, the description supplies the remaining essentials: which platforms, what each entry contains, what is never returned, that the call costs nothing, and where to go when a platform is missing. Nothing an agent needs to select or call it correctly is absent.

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 no parameters (required=[], empty properties), so there is nothing for the description to disambiguate. Baseline of 4 applies for a zero-parameter tool with 100% schema coverage.

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?

Specific verb 'List' plus a precisely scoped resource ('connected publishing accounts per platform') with the platforms named (YouTube, TikTok, Facebook Page, Instagram, Threads). The returned fields (username, reconnect flag, publish mode, AI-disclosure handling, today's limits) make the tool's output scope unmistakable and distinguish it from sibling list_* tools.

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?

Explicitly routes the agent to a named alternative under a stated condition: 'For a platform that is not connected, call autoshort_get_connection_status to get a one-click connectUrl.' This is exactly the when-to-use-something-else guidance an agent needs, and it is tied to an observable state.

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