Skip to main content
Glama
Sign In
Markaestro

Markaestro

Official
by markaestro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get TikTok posting options

get_tiktok_posting_options
Read-onlyIdempotent

Read allowed privacy levels, comment, duet, and stitch availability, and max video length for a connected TikTok creator account before building a Direct Post.

Instructions

Read posting options only for the user's already connected TikTok creator account: allowed privacy levels, whether comments, duets, and stitches can be enabled, and the longest video. Does not publish, change settings, or query arbitrary creators or URLs. TikTok requires a Direct Post to use these, so read them right before building one and pass the chosen privacyLevel in the tiktok settings. Test keys get a sandbox answer without contacting TikTok.

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

Input Schema

NameRequiredDescriptionDefault
productIdNoOn an all-brands connection, the brand whose TikTok account to ask about

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the options are account-scoped, they gate Direct Post construction, and test keys return a sandbox answer without contacting TikTok. It stops short of describing result shape or failure modes (e.g., what happens with no connected account).

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 scope statement is front-loaded, the exclusions follow, and the workflow constraint plus the sandbox caveat close it out. Four sentences, none of which repeat the title or the schema, and no 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?

With no output schema, the description correctly enumerates the returned fields, and with one optional schema-documented parameter the input side needs no further explanation. The Direct Post dependency and sandbox behavior are the details an agent would otherwise get wrong, and both are present.

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 optional productId is fully documented in the schema, so the baseline of 3 applies. The description implies the account is the caller's connected creator account but never mentions the all-brands/brand-selection case, so it adds no meaning beyond the schema here.

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 opens with a specific verb+resource ("Read posting options ... for the user's already connected TikTok creator account") and enumerates exactly what is returned: allowed privacy levels, comment/duet/stitch flags, and max video length. It also explicitly excludes neighboring behaviors ("Does not publish, change settings, or query arbitrary creators or URLs"), which separates it from publish_post and create_post 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?

It states the operative workflow rule: TikTok requires a Direct Post to use these, so read them right before building one and pass the chosen privacyLevel into the tiktok settings. It also lists what the tool is not for, giving an agent both the when and the when-not, plus the downstream dependency.

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