Skip to main content
Glama

List Social Accounts

list_social_accounts
Read-onlyIdempotent

[read] Connected social accounts of the merchant (tokens masked), optionally of one website (website_id or website_uuid). platform = ig|fb|tw|tt|yt|li|th|wp|tg|bsky, or omit for all. Use the returned _account_id as account_id in the other social tools. tg = Telegram user accounts (phone masked, no session/api_hash).

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

Input Schema

NameRequiredDescriptionDefault
platformNo
website_idNo
website_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts beyond the annotations: tokens are masked in the response, and Telegram entries mask the phone and omit session/api_hash. It does not mention pagination or rate limits, so it stops 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.

Conciseness5/5

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

Two dense sentences, front-loaded with the core action and scope, then the platform vocabulary, then the cross-tool handoff, then a Telegram caveat. Every clause carries information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 usefully explains that account identifiers come back as <platform>_account_id and that secrets are masked, which is the key information for a discovery tool. It stops short of describing other returned fields (name, handle, status) or result ordering, which would matter for an agent consuming the list.

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?

Schema description coverage is 0% and no parameter carries an enum, so the description must carry the load — and it does, spelling out the platform code list (ig|fb|tw|tt|yt|li|th|wp|tg|bsky) and the "omit for all" default behavior. website_id and website_uuid are mentioned only as alternative scoping keys, without saying whether they can be combined, so it is not fully compensating.

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 leads with a specific verb and resource ("[read] Connected social accounts of the merchant") and scopes it precisely with the optional website filter. It is easily distinguishable from sibling list tools such as list_ads_accounts or list_sms_accounts because the resource domain is named explicitly.

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?

It gives real workflow guidance: enumerate the allowed platform codes or omit the parameter for all platforms, and use the returned <platform>_account_id as account_id in the other social tools. What it lacks is an explicit exclusion or alternative (e.g. when to prefer a platform-specific get_ig_user or get_tg_channel call instead).

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.