SocialGPT

List connected accounts

list_accounts

Read-only

List the caller's connected social accounts (optional platform filter). Each account_id can be passed to get_account_metrics / list_videos to scope to that account. Accounts are annotated with their account group (brand/workspace) and the envelope includes the caller's groups; pass group_id to filter to one group's accounts. When the list is empty, point the user at connect_url to link an account — newly connected accounts then appear here automatically on the same token (no re-auth).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`group_id`	No	Optional account-group (brand) id from list_accounts. Omit to use the default group.
`platform`	No	Optional platform filter — instagram, tiktok, or youtube (case-insensitive). Omit to span all connected platforms.

Output Schema

TableJSON Schema

Name	Required	Description
`groups`	No	The caller's account groups (brands/workspaces) — pass a group_id to list_accounts / get_content_profile / get_publish_options / publish_post to scope to one.
`reason`	No	Present only when accounts is empty.
`accounts`	Yes
`connect_url`	Yes	Where the user connects (more) social accounts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJul 24, 2026

addedInput schema / properties / group_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional account-group (brand) id from list_accounts. Omit to use the default group."
+}

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"Output of `list_accounts`. `reason`='no_connected_accounts' appears only\nwhen `accounts` is empty; `connect_url` is always present."

addedOutput schema / properties

Added value: +{
+  "accounts": {
+    "items": {
+      "description": "One of the caller's connected social accounts. `account_id` is the handle\nother tools accept (e.g. get_account_metrics, list_videos).",
+      "properties": {
+        "account_group_id": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "account_group_name": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "account_id": {
+          "type": "string"
+        },
+        "display_name": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "is_verified": {
+          "default": false,
+          "type": "boolean"
+        },
+        "platform": {
+          "type": "string"
+        },
+        "profile_link": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "profile_picture_url": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null
+        },
+        "username": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "account_id",
+        "platform",
+        "username"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "connect_url": {
+    "description": "Where the user connects (more) social accounts.",
+    "type": "string"
+  },
+  "groups": {
+    "description": "The caller's account groups (brands/workspaces) — pass a group_id to list_accounts / get_content_profile / get_publish_options / publish_post to scope to one.",
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "reason": {
+    "anyOf": [
+      {
+        "const": "no_connected_accounts",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Present only when accounts is empty."
+  }
+}

addedOutput schema / required

Added value: +[
+  "accounts",
+  "connect_url"
+]

Changed1 schema field changedJun 24, 2026

addedInput schema / properties / platform / description

Added value: +"Optional platform filter — instagram, tiktok, or youtube (case-insensitive). Omit to span all connected platforms."

First observedJun 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description adds that accounts have groups, the envelope includes groups, and newly connected accounts appear automatically. It doesn't contradict annotations.

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?

The description is four sentences with the main purpose in the first sentence. It's efficiently structured without redundant information.

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?

The description covers the main use cases, including empty lists and filtering, but doesn't mention pagination. However, the presence of an output schema may address that.

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?

Schema coverage is 100%, but the description adds value by explaining where to obtain group_id (from the output itself) and how platform filtering works, providing context beyond the schema.

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?

The description clearly states the tool lists the caller's connected social accounts with an optional platform filter. It distinguishes itself from siblings like get_account (singular) and list_videos (different resource) by specifying the resource and scope.

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?

The description provides usage context by explaining how account_id and group_id can be used in other tools, and advises pointing the user to connect_url when the list is empty. It doesn't explicitly exclude alternatives but the purpose is clear.

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

All SocialGPT 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.