Skip to main content
Glama

list_connected_accounts

Read-only

List the social channels connected to the active workspace (LinkedIn profiles and pages, X accounts, and so on), sorted by platform: each one's numeric id, platform and name. platform narrows it to one platform. Use the id in platform_account_ids on schedule_post, queue_post, publish_post or save_draft when a platform has more than one channel. Needs the seat's right to manage connected channels; otherwise it is refused. Not for DemandBird accounts (that is list_accounts).

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

Input Schema

NameRequiredDescriptionDefault
platformNoOptional: filter to one platform
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description earns credit for going beyond them: it states the permission prerequisite (seat must have the right to manage connected channels) and the failure mode (the call is refused), plus the ordering of results and the fields returned. It does not discuss result volume or whether disconnected channels appear, which keeps it off 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?

Purpose and return contents come first, followed by the filter, then the intended downstream use, then the permission constraint and the sibling exclusion. Every sentence supplies information an agent would otherwise have to guess, and nothing is repeated.

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, zero-required-parameter list tool with no output schema, the description covers what comes back (id, platform, name), how it is ordered, and how to reuse the ids elsewhere. The permission refusal and the list_accounts exclusion close the remaining gaps an agent would hit.

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 description coverage is 100%, so both `platform` and `workspace` are already documented; the description's note that `platform` narrows to one platform largely restates the schema. It adds no new syntax or edge-case meaning for the parameters themselves, so the baseline of 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?

Names a specific verb and resource (list the social channels connected to the active workspace) and enumerates the concrete contents returned: numeric id, platform and name, sorted by platform. It also explicitly separates itself from the similarly named sibling list_accounts by ruling out DemandBird accounts.

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 a concrete downstream use case: take the id from this result and pass it in `platform_account_ids` on schedule_post, queue_post, publish_post or save_draft when a platform has multiple channels. It also names the tool NOT to use for DemandBird accounts (list_accounts), so both the use and the exclusion are explicit.

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