Skip to main content
Glama

Read a TikTok account's posting settings

clipember_get_tiktok_creator_info
Read-onlyIdempotent

Read what a connected TikTok account allows right now (TikTok creator_info): who can see a post (privacyLevelOptions — pick one of these, there is no default), which interactions the creator turned off in TikTok (comments, duet, stitch — these must stay disabled), and the longest video it accepts (maxVideoPostDurationSec). Call it before clipember_set_tiktok_choice or a create_post with tiktokOptions, show the options to the user and pass exactly what they pick. Read fresh each time — settings can change.

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": "clipember_get_tiktok_creator_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdNoWhich TikTok account (clipember_list_platform_connections); omit for the default one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral constraints: privacy has no default so a choice is mandatory, creator-disabled interactions must remain disabled, and values can change between calls so caching is unsafe. This is precisely the kind of pre-condition and volatility disclosure a caller needs.

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 purpose, then the call-ordering rule — no filler sentences. The heavy nested-parentheses and em-dash clauses make it dense to scan, costing some clarity against its otherwise tight structure.

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?

With no output schema, the description carries the full burden of explaining return values and does so by naming all three fields it yields. Combined with the ordering rule and the no-default warning, an agent has everything needed to invoke and use the result.

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?

Only one parameter (connectionId) and schema coverage is 100%, with the schema documenting "omit for the default one" and pointing at clipember_list_platform_connections. The description adds nothing about the parameter beyond what the schema already states, so the baseline 3 applies.

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 ("Read what a connected TikTok account allows right now") and names the underlying TikTok concept (creator_info), then enumerates the three returned facts: privacyLevelOptions, disabled interactions, and maxVideoPostDurationSec. An agent can distinguish it from clipember_set_tiktok_choice or get_account_settings without opening a schema.

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 states when to call it ("before clipember_set_tiktok_choice or a create_post with tiktokOptions"), what to do with the result ("show the options to the user and pass exactly what they pick"), and the refresh rule ("Read fresh each time — settings can change"). It also names the alternative it is not, routing ordering clearly.

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.

Resources