Skip to main content
Glama

Eurekuh

TikTok video performance

get_video_stats
Read-onlyIdempotent

Views, likes, comments and shares for every public video on a connected TikTok account, newest first, as TikTok reports them now. Match a video to a post by its description (the caption) and createTime (unix seconds). TikTok has no API to delete a published video: that has to be done in the TikTok app.

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_video_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdNoA TikTok account id from list_accounts. Defaults to the organization's default TikTok account.
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real behavior beyond them: values are whatever TikTok reports at call time (freshness caveat), results are ordered newest first, and the delete limitation prevents wasted attempts at an unsupported operation. Pagination and rate-limit behavior remain unspecified.

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 tight sentences with the payload description front-loaded and no filler. The closing deletion note is slightly tangential to a read-only stats tool but earns its place by heading off an unsupported action.

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?

There is no output schema, and the description compensates by enumerating the returned metrics and their ordering, plus the keys needed to join videos to posts. It does not say whether the result set can be truncated for large accounts, which is the main remaining gap.

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 description coverage is 100% and both parameters already document their sourcing (list_accounts, list_organizations) and defaulting behavior. The description adds no further meaning about accountId or organizationId, 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?

Names a specific resource (public videos on a connected TikTok account) and the exact metrics returned (views, likes, comments, shares), plus the ordering (newest first). The TikTok platform qualifier alone separates it from get_instagram_stats without requiring the agent to open either schema.

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 actionable context: use description (caption) plus createTime in unix seconds to correlate a video back to a post, and states that deleting a published TikTok video is impossible via API so it must be done in the app. It stops short of an explicit 'use this instead of X' statement against sibling tools, so it is clear context rather than full routing guidance.

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