PostNitro

List Social Accounts

postnitro_list_social_accounts

Read-onlyIdempotent

List the connected social accounts in your workspace, grouped by platform (linkedin, instagram, tiktok, threads).

These account IDs are what you pass as selectedAccounts when creating a scheduled post. All four platform arrays are always present (empty when none connected).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Total connected accounts across all platforms
`accounts`	Yes	Every connected account, flattened across platforms

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark it as read-only and idempotent. The description adds useful behavioral detail that all platform arrays are always present, even when empty.

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?

Description is concise, well-structured, and directly communicates the tool's purpose and output behavior without unnecessary detail.

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?

Provides enough context for an agent to know when to call it and what to expect, including the always-present empty arrays. Lacks a detailed output schema, but the simple grouped-list behavior is sufficiently described.

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 has no parameters, and the description accurately reflects that. No parameter explanation is needed.

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?

Clearly states the tool lists connected social accounts grouped by platform, and distinguishes the account IDs as the values used for selectedAccounts in scheduled post creation.

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?

Explains when the returned IDs are needed (for creating scheduled posts) and notes the grouping. It does not explicitly contrast with get_social_account, but the purpose is clear enough for correct selection.

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

All PostNitro tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools are clearly separated by verb and noun (generate_carousel vs generate_image vs generate_video, import_* vs generate_*). The generic convenience names like generate_and_wait and import_and_wait are slightly ambiguous, but their descriptions and the _wait/_schedule suffixes make them distinguishable.

Naming Consistency4/5

All tools share the postnitro_ prefix and snake_case verb-first convention. A few compound names (generate_and_schedule, import_and_wait) break the strict verb_noun pattern, but the convention is otherwise consistent and predictable.

Tool Count2/5

With 35 tools, the surface exceeds the rubric's 25+ 'too many' threshold. Many entries are convenience wrappers (_wait, _and_schedule) around the same core operations and could be consolidated to reduce overload.

Completeness4/5

The domain is well covered: generation, import, output retrieval, scheduling, brands, social accounts, audio, templates, presets, and defaults. Minor gaps remain (no delete_brand, no upload/connect for audio/social accounts), but those are largely external or non-critical.

Resources

Need Help?