List connected social accounts in the SocialClaw workspace. Optionally filter by provider (x, facebook, instagram_business, instagram, linkedin, linkedin_page, pinterest, tiktok, telegram, discord, youtube, reddit, wordpress).
| Name | Required | Description | Default |
|---|---|---|---|
| provider | No | Optional provider filter. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It indicates a read-only listing operation ('List') and that it shows 'connected' accounts, but does not disclose details like rate limits, pagination, or authorization requirements. For a simple read operation, the behavior is mostly transparent, but the description could add more safety info.
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?
The description is a single sentence that clearly states the purpose and then lists provider options. No wasted words, and the key action is front-loaded. The provider list is long but necessary for usability.
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?
For a simple one-parameter list tool, the description is mostly complete: it names the workspace, the resource type, and the filter. It does not mention the return format or pagination, but with no output schema, the implicit expectation is a list of account objects. Could be slightly more explicit but is adequate.
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?
Schema coverage is 100%, so the schema fully documents the single 'provider' parameter. The description adds value by enumerating accepted provider values (x, facebook, etc.) which are not in the schema as enums. This extra context helps agents select valid filters.
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 'List connected social accounts in the SocialClaw workspace' with a specific verb and resource. It distinguishes from sibling tools like connect_account or list_posts by focusing on accounts.
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 implies when to use this tool: when you need to see connected accounts. It also mentions an optional filter, but does not explicitly exclude alternatives or state when not to use it. The context is clear, though no exclusionary guidance is provided.
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.
Most tools have clearly distinct purposes, but a few are close: delete_instagram_comment vs hide_instagram_comment overlap (though one is preferred), and get_analytics overlaps with Instagram-specific analytics tools. Overall, the boundaries are generally clear, with only minor potential confusion.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_accounts, connect_account, upload_asset, cancel_post). There are no deviations in style or grammar, making the naming highly predictable.
With 31 tools, this exceeds the 25-tool threshold for 'too many'. While the broad multi-provider social media domain justifies some breadth, the sheer number makes the surface heavy and potentially overwhelming, pushing the score down.
The tool set covers core workflows well: account connection, scheduling/publishing, post management, analytics, Instagram-specific engagement (comments, messages), asset upload, and workspace health/usage. Minor gaps include no explicit disconnect_account or delete_post, but these are edge cases; the domain is largely covered.
