Get all connected social media accounts across all platforms
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of accounts to return per platform | |
| platform | No | Filter by platform or get all platforms | all |
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 carries the full burden. It does not disclose behavioral traits such as pagination, rate limits, authentication requirements, or return format. Additionally, saying 'all' conflicts with the schema's 'limit' parameter (default 10), which limits results per platform.
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, concise sentence that directly states the tool's purpose without extraneous information. It is front-loaded and easy to parse.
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 the simple nature of the tool (two optional parameters, no output schema) and full schema coverage, the description is minimally sufficient. However, the lack of annotation and output schema means it does not explain what the return value looks like or that 'all' accounts are limited by the 'limit' parameter, leaving room for ambiguity.
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 description coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond the schema; the phrase 'across all platforms' aligns with the 'platform' parameter but does not clarify the 'limit' parameter's behavior or the meaning of 'connected accounts.'
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 the tool retrieves all connected social media accounts across all platforms, using a specific verb ('Get') and resource ('accounts'). It distinguishes itself from sibling tools like get_all_posts by focusing on accounts, not posts.
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 provides no guidance on when to use this tool versus alternatives, nor does it mention exclusions or context. It simply states what the tool does without explaining its role relative to siblings like get_all_posts or schedule_post.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
