Ravenpost

List connected accounts

list_accounts

Read-onlyIdempotent

List the social accounts connected to one workspace (Instagram, TikTok, X, Telegram, LinkedIn, Threads, Bluesky, YouTube and Pinterest; an account connected before its network was withdrawn still lists under its own platform). Returns each account id, platform, username, status, connection and captionMax — that account's own caption budget, which create_post holds its caption to. For X it depends on the account: xPremium true means X Premium and 25,000 characters, false means 280; X counts every link as 23 and each emoji or symbol such as → − • … as 2. Use an account id as a target when creating a post. Accounts belong to a single workspace, so with several workspaces give workspaceId (see list_workspaces) — an account id from one workspace is rejected by a post created in another. connection is only meaningful for Instagram: "FACEBOOK_LOGIN" accounts were connected through a Facebook Page and are the only ones that can browse and attach reel audio (list_audio) or invite collaborators; "INSTAGRAM_LOGIN" accounts — the way Instagram connects today — publish normally but can do neither.

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

Input Schema

Name	Required	Description	Default
`workspaceId`	No	Which workspace to act in — an id from list_workspaces. Optional with a single workspace; REQUIRED once there are several, where guessing would mean posting one client's content to another client's accounts. Ask the user which one before publishing.

Output Schema

Name	Required	Description	Default
`accounts`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Well beyond the readOnlyHint/idempotent annotations: it discloses that accounts connected before a network was withdrawn still appear under their platform, explains captionMax semantics per account, spells out X's character counting (25,000 vs 280, links as 23, emoji/symbols as 2), and warns that an account id from one workspace is rejected by a post in another.

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?

Front-loaded with the core action and platform scope, then progressively layers operational detail. It is dense and long, and the granular X character-counting rules sit heavily for a listing tool, but each clause traces back to a decision the agent must make when picking an account.

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 1-parameter read tool with full annotations and an output schema, this covers everything: what is returned conceptually, workspace scoping, platform coverage, and the platform-specific nuances (Instagram connection types, caption budgets) an agent needs before choosing an account id to post with.

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% for the single workspaceId parameter, so the schema already carries the full explanation including the multi-workspace risk. The description adds only the cross-reference to list_workspaces and the cross-workspace rejection consequence, 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?

Opens with a specific verb + resource + scope: 'List the social accounts connected to one workspace', then enumerates exactly which platforms are covered and notes the legacy-withdrawn-network case. An agent can distinguish this from list_workspaces and the post-creation siblings immediately.

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?

Gives clear operating context: use the returned account id as the target for create_post, pass workspaceId when several workspaces exist, and consult list_workspaces for the id. It also routes to list_audio for reel audio. It stops short of explicit exclusions (e.g. 'do not use this to look up a single account'), so it is strong but not a full when/when-not statement.

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

All Ravenpost tools Inspect

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.