Skip to main content
Glama

Sociality.io Social Media MCP

List connected social accounts

social_accounts_list
Read-only
Use this when the user asks which of their own social media accounts are in their Sociality.io workspace, or before calling social_account_stats_list or social_account_posts_list, which need an account ID from this list. Returns each account's ID, name, username, channel and whether its connection is active (is_token_active). Filter by channel or by name. Do not use it for competitors or other public accounts the user does not manage: social_competitors_list covers those.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOnly return accounts whose name or username contains this text, for example "pepsi".
pageNoPage number, starting at 1. Each page has up to 50 accounts; check pagination.has_more for more.
channelNoOnly return accounts on this channel: facebook, instagram, x, linkedin, tiktok or youtube.

Output Schema

NameRequiredDescriptionDefault
accountsYesList of social media accounts the user has access to.
_envelopeYesVersioned response envelope metadata.
paginationYes
action_requiredNoPresent only when a user action is required before this request can be answered. The data block is empty and no credits were charged. Do not re-call this tool with different arguments or a wider date range; the workspace needs a change first, unless the action says how to adjust the call or names a tool that makes the change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / channel / description
      Previous value: -"Filter accounts by channel."New value: +"Only return accounts on this channel: facebook, instagram, x, linkedin, tiktok or youtube."
    • changedInput schema / properties / name / description
      Previous value: -"Filter accounts by name or username (contains)."New value: +"Only return accounts whose name or username contains this text, for example \"pepsi\"."
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination (default: 1)."New value: +"Page number, starting at 1. Each page has up to 50 accounts; check pagination.has_more for more."
  2. Changed3 schema fields changed
    • changedOutput schema / properties / action_required / description
      Previous value: -"Present only when a user action is required before this request can be answered. The data block is empty and no credits were charged. Do not re-call this tool with different arguments or a wider date range; the workspace needs a change first, unless the action says how to adjust the call."New value: +"Present only when a user action is required before this request can be answered. The data block is empty and no credits were charged. Do not re-call this tool with different arguments or a wider date range; the workspace needs a change first, unless the action says how to adjust the call or names a tool that makes the change."
    • changedOutput schema / properties / action_required / properties / action / description
      Previous value: -"The action the user must take before this data becomes available."New value: +"The action that unblocks this request. When it names a tool, call that tool from the conversation; otherwise the user takes it in Sociality."
    • changedOutput schema / properties / action_required / properties / link / description
      Previous value: -"Sociality URL where the user takes that action."New value: +"Sociality URL where the user takes that action themselves."
  3. Changed4 schema fields changed
    • changedOutput schema / properties / accounts / items / properties / created_at / description
      Previous value: -"The creation timestamp of the social media account."New value: +"The creation timestamp of the social media account (ISO 8601)."
    • changedOutput schema / properties / accounts / items / properties / created_at / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / accounts / items / properties / updated_at / description
      Previous value: -"The last update timestamp of the social media account."New value: +"The last update timestamp of the social media account (ISO 8601)."
    • changedOutput schema / properties / accounts / items / properties / updated_at / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), yet the description still adds substance: the returned fields including the is_token_active connection flag, and that the list is scoped to the user's own workspace. It does not discuss result volume or failure modes, which keeps it below 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?

Three sentences, front-loaded with the use condition, then the prerequisite, then the exclusion. Every sentence carries decision-relevant information; nothing is padding.

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 read-only 3-parameter listing tool with a full schema, annotations and an output schema, the description covers trigger, prerequisites, return shape and scope boundary. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% with enum and paging semantics documented inline, so the schema carries the parameter burden. The description only restates 'filter by channel or by name' without adding syntax or precedence rules for combining filters, so the baseline 3 applies.

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?

States a specific verb and resource ('List connected social accounts') plus the exact fields returned, and names the sibling it must not be confused with (social_competitors_list). An agent can distinguish it from social_account_posts_list/social_account_stats_list purely from the text.

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?

Gives an explicit when-to-use trigger ('user asks which of their own social media accounts are in their workspace'), a sequencing rule (call this before stats/posts tools that need an account ID), and an explicit when-not-to-use with the alternative (competitors → social_competitors_list).

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.