Skip to main content
Glama

List accounts

list_accounts

List the connected social accounts of the API key's workspace across all networks, YouTube channels, Bluesky accounts and Google Business Profile locations included (use the account id as accountId in create_post). Optional channel filter; unavailableChannels names networks whose accounts could not be loaded. Requires scope ACCOUNTS_READ.

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
channelNoOnly accounts of this network, e.g. TIKTOK (UPPERCASE canonical, lowercase accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the required scope ACCOUNTS_READ (auth prerequisite) and explains that `unavailableChannels` names networks whose accounts failed to load, which is real partial-failure behavior an agent could not infer from the schema. It stops short of describing pagination, ordering, or expected volume.

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 no filler, but several distinct facts (scope, filter optionality, unavailableChannels, create_post linkage) are compressed into one long run-on sentence, which makes the secondary details easier to miss than separate clauses would.

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?

For a one-param read-only list tool with no output schema and no annotations, the definition covers the essentials: what is returned conceptually, the auth scope, the filter, and the one notable response field (`unavailableChannels`). It does not describe the structure of the returned account objects, which is the main remaining gap given the absence of an output schema.

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% — the single `channel` parameter already documents its enum with an example and casing note. The description only calls it an "optional channel filter," adding no meaning beyond the schema, 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?

Specific verb+resource+scope: "List the connected social accounts of the API key's workspace across all networks," and it enumerates the notable subtypes (YouTube channels, Bluesky accounts, GBP locations). It is clearly distinguishable from list_brands or list_approvers and even states the resulting identifier's downstream use.

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 concrete usage context — "use the account id as accountId in create_post" — and notes the channel filter is optional. There is no explicit when-not guidance or named alternative, but for a single-purpose enumeration tool the context provided is clear and actionable.

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