Skip to main content
Glama
Sign In
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List profiles

list_users
Read-only

Retrieve all account profiles and their connected social accounts before publishing. Gets exact profile names and verifies which target platforms are connected or need reconnecting.

Instructions

List all Upload-Post profiles in the account, with their connected social accounts. Call this FIRST, before publishing, to get the exact profile name (user) and check that the target platforms are connected; never invent a profile name. When the account has no profile, or the requested platform is not connected or needs reconnecting, the response carries next_step and connect_url: give the user that link, ask them to tell you when they have connected, and wait — do not try to publish meanwhile. The TikTok account object carries a capabilities array (music, location, cover_image, cover_timestamp, draft, photo_privacy, video_privacy, inbox_fallback, profile_analytics) telling which optional TikTok fields that connection accepts.

Input Schema

NameRequiredDescriptionDefault
platformsNoOptional platforms the user wants to publish to (e.g. ['tiktok','instagram']). When given, the response says whether they are connected and, if not, how to connect them.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.17.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / platforms
      Added value: +{
+  "description": "Optional platforms the user wants to publish to (e.g. ['tiktok','instagram']). When given, the response says whether they are connected and, if not, how to connect them.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed2 schema fields changedv0.11.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. First observedv0.4.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare this a safe read; the description adds substantive behavior beyond that: the response carries next_step/connect_url on failure states, and the TikTok account object exposes a capabilities array listing which optional fields the connection accepts. It also defines a wait-and-retry workflow the agent must not short-circuit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the 'call FIRST' imperative, then layered with failure handling and platform-specific detail. Dense but every sentence carries operational meaning; the long parenthetical capability enumeration is the only mildly heavy element.

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?

Covers the full pre-publish discovery workflow, what to do on the not-connected path, and the platform-specific capability surface, while an output schema exists to carry return shape. Nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100% and the single `platforms` parameter is fully documented in the schema, so the baseline applies. The description references "the target platforms" and the connected/not-connected response behavior, which adds a little context but no syntax or format detail beyond the schema.

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?

States a specific verb and resource ("List all Upload-Post profiles") plus scope ("in the account, with their connected social accounts"). It is clearly separable from siblings like create_user, delete_user, and get_account_info.

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 says to call this FIRST before publishing, forbids inventing a profile name, and prescribes the exact behavior when a platform is missing or needs reconnecting (surface connect_url, wait for user confirmation, do not publish meanwhile).

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

Deploy Server

Other Tools