AutoPoster AI

List Connected Accounts

autoposter_list_accounts

Read-only

Lists all connected social media accounts (X, LinkedIn, Instagram, TikTok, YouTube, Threads, Bluesky, Pinterest, Facebook) in the current Autoposter workspace.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`accounts`	Yes	List of active connected accounts in the workspace.
`timezone`	No	Default timezone for the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accounts": {
+      "description": "List of active connected accounts in the workspace.",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Account ID.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Account display name.",
+            "type": "string"
+          },
+          "platform": {
+            "description": "Platform name (e.g. twitter, linkedin, instagram).",
+            "type": "string"
+          },
+          "username": {
+            "description": "Account username or handle.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "platform",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "timezone": {
+      "description": "Default timezone for the workspace.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "accounts"
+  ],
+  "type": "object"
+}

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine value by scoping results to the 'current Autoposter workspace', which the annotations do not convey. It stops short of describing result shape, but an output schema exists to carry that.

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?

A single front-loaded sentence that identifies the resource, its platform coverage, and its workspace scope with no filler. Nothing in it is redundant with the title or name.

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 zero-parameter, read-only list operation with an output schema and full annotation coverage, the description supplies everything an agent needs to select and call it. Return values are legitimately delegated to the output schema.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline of 4 applies. The description correctly avoids inventing filters that the schema does not support.

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?

States a specific verb ('Lists') and resource ('connected social media accounts') with an explicit scope ('current Autoposter workspace') and enumerates the supported platforms. This clearly separates it from sibling list tools such as autoposter_list_posts and autoposter_list_media.

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?

Usage is implied rather than stated: an agent can infer this is the discovery step for obtaining account handles/IDs before drafting or scheduling posts. There is no explicit when-to-use guidance, no mention of prerequisites, and no named alternative, but for a zero-parameter read tool the space of alternatives is narrow.

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

All AutoPoster AI 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.

Resources

Need Help?