Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Channel Tiktok Creator Info

channel_tiktok_creator_info
Read-onlyIdempotent

Fetches a TikTok channel's available privacy levels, comment, duet, and stitch permissions, and maximum video length so you can choose a valid privacyLevel for scheduled posts.

Instructions

What a TikTok channel may post right now, read from TikTok: the privacy levels the account offers, whether comments, duets and stitches can be allowed and the longest video. A TikTok target of post_schedule needs a privacyLevel from this list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>",
      "channelId": "<channelId>"
    },
    "name": "channel_tiktok_creator_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYesThe channel id (see channel_list).
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.2/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 openWorld, so the safety profile is covered. The description adds value beyond them by naming exactly which fields come back and making clear the answer is read live from TikTok (an external, potentially variable source) rather than cached configuration. It does not mention latency, rate limits, or channel-disconnected failures.

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?

Two sentences, front-loaded with the payload content, then the actionable dependency. No filler and nothing repeated from the schema or annotations.

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?

No output schema exists, so the description must convey returns, and it does so at a useful level of specificity (privacy levels, interaction flags, max duration). It is essentially complete for a simple two-parameter read; only error/empty conditions are unaddressed.

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?

With 100% schema description coverage on both parameters (channelId points to channel_list, organizationId to organization_list), the schema already carries full meaning. The description adds nothing about the parameters, which is acceptable but not additive, so 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 resource read ("What a TikTok channel may post right now, read from TikTok") and enumerates the returned facts: privacy levels, comment/duet/stitch allowances, max video length. This clearly distinguishes it from channel_get/channel_list, which handle channel records rather than TikTok posting constraints.

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

Usage Guidelines4/5

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

Gives concrete when-to-use context by tying it to post_schedule: a TikTok target needs a privacyLevel from this list. It stops short of stating exclusions (e.g. when to prefer channel_get for general channel data), so it is clear but not fully routing.

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