list_accounts
List the connected social accounts on this Postlia workspace.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Postlia
by com.postlia
TDQS
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full burden. It describes a safe read operation ('list') but offers no additional behavioral details such as pagination, ordering, or rate limits. For a parameterless tool, this is adequate.
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?
The description is a single, concise sentence that clearly conveys the tool's purpose with no unnecessary words.
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?
Given the tool has no parameters, no output schema, and no annotations, the description provides sufficient information to understand the tool's function. It is complete for a simple list operation.
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?
There are zero parameters, so the description does not need to provide parameter-level detail. Baseline score of 4 applies per guidelines.
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?
The description explicitly states the verb 'list' and the resource 'connected social accounts', and specifies the context 'on this Postlia workspace'. It clearly distinguishes from sibling tools which deal with posts.
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?
The description implies usage when the user needs to see connected social accounts, but does not explicitly say when to use vs alternatives. However, sibling names like 'cancel_post' and 'create_post' make the distinction clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
Each tool targets a unique resource and action: drafts, scheduled posts, published posts, accounts, analytics, quota, and queue info are all clearly separated. No two tools overlap in purpose; even similar-sounding ones like list_scheduled_posts and list_published_posts are distinct.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_post, list_drafts, get_posting_quota). The use of 'list_' for collections and 'get_' for single items/summaries is predictable and logical.
Tool Count5/5
14 tools is well within the ideal 3-15 range and appropriately covers the domain of social media post management, scheduling, drafts, analytics, and account inspection. Each tool serves a distinct function without redundancy.
Completeness4/5
The surface covers the full lifecycle of posts and drafts: create, read, update, delete, schedule, cancel, and reschedule. Minor gaps exist, such as no direct way to convert a draft into a post, but this can be worked around by copying content.