Skip to main content
Glama

List social accounts

list_social_accounts
Read-only

List the social accounts (TikTok, YouTube, Instagram, X, Facebook Pages, webhooks) and channels connected to the Revid account or active workspace, without tokens. Call this before publish_now or schedule_publish to pick a destination: pass accounts[].id as <platform>.id (or accounts[].username as <platform>.username, facebook.name for Pages), or channels[].id as channelId. Accounts with tokenInvalid: true must be reconnected by the user in Revid settings before publishing.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
methodYes
statusYes
endpointYes
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, yet the description still adds material behavior: results are returned "without tokens" (no credential exposure), and accounts with tokenInvalid: true require the user to reconnect in Revid settings before publishing. That is a real prerequisite/workflow constraint an agent could not derive from the annotations.

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?

Two sentences, front-loaded with the purpose and then the routing instructions, with no filler. The middle clause packs several mappings into one dense sentence, which is efficient but slightly hard to parse on first read.

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?

An output schema exists, so return-value detail is not required, and the description covers the remaining gaps: what is listed, when to call it, how to use the identifiers, and the tokenInvalid remediation path. Nothing an agent needs in order to call and act on this tool is missing.

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, so the baseline is 4 and the empty schema leaves nothing to clarify. The description instead documents the shape of the values consumed downstream (<platform>.id, <platform>.username, facebook.name, channelId), which is useful but concerns other tools' inputs rather than this one's.

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 the social accounts ... and channels") and enumerates the platforms covered (TikTok, YouTube, Instagram, X, Facebook Pages, webhooks). It also scopes the result to the Revid account or active workspace, which no sibling list_* tool claims, so an agent can distinguish it immediately.

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 names the downstream alternatives and the trigger: "Call this before `publish_now` or `schedule_publish` to pick a destination." It goes further and prescribes how to feed the results into those tools (accounts[].id as `<platform>.id`, channelId, etc.), leaving nothing to inference.

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