Skip to main content
Glama

List profiles and accounts

list_profiles
Read-onlyIdempotent

Your posting profiles, each with its connected social accounts: id, network, username, status and postable. Post only to accounts with postable: true; not_postable_reason says why not (reconnect needed, or X: coming soon). A postable TikTok account also has tiktok.privacy_level_options: the audiences it allows (e.g. PUBLIC_TO_EVERYONE, SELF_ONLY); ask the user which one before posting there.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
profilesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real context beyond that: what 'postable' gates, what 'not_postable_reason' encodes (reconnect needed, X coming soon), and the extra tiktok.privacy_level_options payload with an example enum and a user-confirmation requirement.

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?

Three sentences, front-loaded with the resource and its fields, then the actionable gating rules. Dense but every clause carries information; the parenthetical examples are short and illustrative rather than padding.

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?

An output schema exists, so return shape needn't be explained, and the description still surfaces the two decision-relevant fields (postable, not_postable_reason) plus the TikTok-specific pre-post requirement. Nothing an agent needs to act on the result is missing.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description does not waste space inventing argument semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely: 'Your posting profiles, each with its connected social accounts', and enumerates the fields returned (id, network, username, status, postable). This is enough for an agent to distinguish it from list_posts, list_characters, or whoami, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

It gives explicit consumption rules – 'Post only to accounts with postable: true' and 'ask the user which one before posting there' – which is genuinely useful gating guidance. However, it never states when to call this tool versus alternatives (whoami, list_posts), so tool-selection guidance is absent; usage is only implied by the field semantics.

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.