Skip to main content
Glama

uplika

by com.uplika

List connected accounts

list_accounts
Read-only

Connected social accounts. Call this before publishing anything. Each item has id, platform (threads etc.), handle and status. The accountIds you pass to publish are these ids, and only "active" ones publish. If the person did not name a channel, target every active account. If the list is empty, no channel is connected yet. Send the person to https://uplika.com/dashboard/connections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdNoWhich workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds non-obvious behavioral context: the meaning of status 'active', that only active accounts are used for publishing, and that an empty list indicates no connected channel. This goes beyond the annotation without contradicting it.

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?

Every sentence adds value, starting with the core purpose, then usage context, output fields, and edge-case guidance. It is front-loaded and contains no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite lacking an output schema, the description explains the item fields and key statuses, integrates with the publish workflow, and covers the empty-list case with a suggested action. This is complete for a read-only list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description itself does not discuss the workspaceId parameter, but the schema provides a thorough parameter description including when it is needed and explicit guidance not to re-ask. With 100% schema coverage, the description adds little parameter-level meaning, earning the baseline 3.

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 clearly states this tool lists connected social accounts, enumerating fields (id, platform, handle, status). It distinguishes itself from sibling tools by explicitly positioning it as the precursor to publishing, and it is uniquely named 'list_accounts' with no similar sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs 'Call this before publishing anything' and explains how the output maps to publish (accountIds, only active accounts, targeting all active accounts when no channel is named). Also provides an actionable fallback when the list is empty, sending the person to the dashboard.

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

All uplika toolsInspect
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.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, and descriptions actively steer usage (e.g., get_post vs open_post, list_posts vs list_channel_posts). A few pairs like list_accounts vs select_channels or get_post vs open_post still require careful reading to pick the right one, but the overlap is manageable.

Naming Consistency4/5

The dominant pattern is verb_noun (delete_post, get_insights, list_accounts, select_channels), which is consistent and predictable. A few bare-verb names like publish and reply, plus the media_* prefixed tools, break the strict pattern but still feel coherent within their subdomains.

Tool Count4/5

20 tools is on the heavier side, but the breadth is justified by the server's scope: publishing, media upload workflows, reply threads, insights, quotas, and account selection. Each tool has a real job, though the four post-retrieval variants and five media tools could feel redundant at a glance.

Completeness4/5

The core lifecycle is well covered: publish, reply, delete, retry, retrieve, list, and get insights, plus multi-step media handling. Minor gaps exist, such as no general post editing, no delete-reply action beyond hiding, and limited scheduling outside YouTube, but these are not critical for the stated purpose.

Resources