accounts_listList all connected social media accounts.
Returns the platform, username, and account ID for each connected account. Use this to find account IDs needed for creating posts.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and destructiveHint annotations already cover the safety profile, so the description doesn't need to repeat that. It does add that all accounts are returned rather than one, and identifies the resolution of output fields, but no deeper behavior like pagination or rate limits is discussed. This is acceptable given the zero-parameter and output schema context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Every sentence earns its place: the first states the operation, the second describes the return contents, and the third gives the primary use case. No filler, front-loaded, and appropriately short.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a zero-parameter schema, output schema, and clear read-only annotations, this description is complete. It answers what, when, and why to call it, and connects to a real downstream need (creating posts) which helps agents compose workflows.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the description has no burden to explain parameter semantics. The 100% schema coverage and empty properties are self-evident; baseline 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool lists all connected social media accounts, naming the exact resource and scope. It also specifies the fields returned (platform, username, account ID), which differentiates it from account-level sibling tools like accounts_get, accounts_get_follower_stats, and health checks.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a concrete use case: 'Use this to find account IDs needed for creating posts.' This is clear guidance for when to apply the tool, though it doesn't explicitly state when not to use it or name alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools are clearly separated by domain prefix, but several overlap: posts_publish_now duplicates posts_create's publish_now mode, posts_edit_post vs posts_update is confusing without reading both descriptions, and analytics_get_analytics broadly overlaps the more specific analytics metrics tools. The descriptions do help disambiguate, but the large number of similar post/analytics helpers still creates selection risk.
Most tools follow a readable lower_snake resource_verb format, with domains like accounts_, posts_, profiles_, and queue_. However, there is notable drift: redundant suffixes (queue_create_queue_slot, tracking_tags_get_tracking_tag_stats), singular/plural mismatch (account_groups_ vs accounts_), non-prefixed helpers (call_tool, search_tools, docs_search), and paired verbs that seem arbitrary (posts_edit_post vs posts_update). It is readable but not cleanly consistent.
51 tools is far above the range where an agent can quickly select the right one, and many entries are wrappers or variants: publish_now, edit_post, retry_all_failed, and multiple analytics/queue helpers could be consolidated. The broad domain justifies more tools than a tiny server, but this count is excessive and will add navigation overhead.
The server covers the core social media management lifecycle well: profiles, accounts, posts, scheduling, queueing, analytics, comments, mentions, media uploads, tracking tags, and usage billing are all represented. There are minor gaps—tracking tags are read-only, there is no direct account connection/disconnection flow, and published-post deletion is unsupported—but agents can complete the main workflows with these tools.