Skip to main content
Glama

List connected accounts

list_accounts
Read-only

Retrieve an organization’s connected social accounts and connection status to diagnose why posts fail and filter accounts by network or supported capability.

Instructions

The social accounts connected to an organization: network, name, follower count and whether the connection is broken. An account with error_code other than 0 cannot publish until a person reconnects it, and that is usually the answer to 'why did this post not go out'. On LinkedIn, personal_profile marks the person's own profile, as opposed to the pages they manage. On TikTok, tiktok_comments says whether that account's comment inbox is turned on.

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

NameRequiredDescriptionDefault
limitNo
offsetNo
capabilityNoOnly accounts whose network supports this capability.
social_networkNoFilter by network, e.g. ['instagram', 'linkedin'].
id_organizationNoThe PlanVortex organization id. Optional: resolved automatically when there is only one to choose from, or when the server was configured with a default one.

Output Schema

NameRequiredDescriptionDefault
totalYes
accountsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • addedOutput schema / properties / accounts / items / properties / tiktok_comments
      Added value: +{
      +  "description": "TikTok only. false: this account has no comment inbox until a person turns comments on in the PlanVortex panel.",
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changedv0.11.1
    • changedInput schema / properties / id_organization / description
      Previous value: -"The PlanVortex organization id. Optional: if this app reaches a single organization, or the server was configured with a default one, it is resolved automatically."New value: +"The PlanVortex organization id. Optional: resolved automatically when there is only one to choose from, or when the server was configured with a default one."
    • addedOutput schema / properties / accounts / items / properties / personal_profile
      Added value: +{
      +  "const": true,
      +  "description": "A LinkedIn personal profile: it publishes, but has no comment inbox.",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changedv0.7.0
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare a read-only, non-destructive, closed-world operation, so the safety profile is covered. The description adds real behavioral context beyond that: an error_code other than 0 blocks publishing until a person reconnects, and the LinkedIn/TikTok field flags change meaning per network. It omits pagination behavior despite limit/offset existing.

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 statement of what is returned, followed by two tightly scoped, network-specific clarifications. Every sentence carries information; the only mild weakness is that return-field detail crowds out input guidance.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so explaining return fields is not strictly required, yet that is where nearly all the description's effort goes. For a five-parameter list tool it leaves gaps on pagination, default limits, and what happens when id_organization cannot be auto-resolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 60%, the description should compensate for the undocumented limit and offset parameters, but it never mentions any of the five parameters. The fields it does explain (error_code, personal_profile, tiktok_comments) are return values, not inputs, so they add nothing to invocation semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource and enumerates what each entry carries (network, name, follower count, broken-connection flag), so an agent knows this returns the org's connected social accounts. It stops short of naming a verb or differentiating itself from siblings like get_account_metrics or get_social_capabilities, which an agent could plausibly confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is one implicit use case framed as a diagnostic: 'that is usually the answer to why did this post not go out.' That is useful but narrow, and no explicit when-to-use / when-not-to-use versus alternatives (e.g. metrics or capabilities tools) is given.

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