Skip to main content
Glama

list_tiktok_posts

Retrieve TikTok posts with engagement metrics and aggregated statistics. Filter by account, timeframe, and sort by views, likes, shares, comments, or bookmarks.

Instructions

List TikTok posts with engagement metrics and aggregated statistics.

Args: timeframe: 7, 30, 90, or "all" (default 30). sort: "recent", "views", "likes", "shares", "comments", "bookmarks". tiktok_account_id: Filter by account. limit: Default 20, max 200. offset: Pagination offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo
limitNo
offsetNo
timeframeNo
tiktok_account_idNo
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'List,' which implies read-only, but doesn't explicitly state safety, authentication requirements, rate limits, or any side effects. It also doesn't explain aggregation behavior or timezone handling for timeframe.

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 description is compact and front-loaded. It uses a single sentence for the purpose and a bullet-like list for parameters, with no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with 5 optional params and no output schema, the description covers parameters well but lacks details on the return structure beyond 'engagement metrics and aggregated statistics.' It also doesn't mention pagination behavior or rate limits, which may be important for a list operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant meaning by specifying allowed values for timeframe (7, 30, 90, 'all'), sort options, and default/max for limit, plus the meaning of offset and filter. This fully compensates for the schema's 0% coverage.

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 clearly states it 'List TikTok posts with engagement metrics and aggregated statistics,' using a specific verb and resource that distinguishes it from sibling tools like list_videos or list_tiktok_accounts.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. The sibling list_videos and get_video_analytics could overlap, but the description doesn't mention them or any exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AhmadElsaeedd/reelfarm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server