Skip to main content
Glama

Like a TikTok video

tiktok_like

Like a video on TikTok using a connected local account. Specify the account ID and video URL to perform the like.

Instructions

Like a video from a connected local profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_urlYes
account_idYesLocal account name using letters, numbers, dots, dashes, or underscores
Behavior2/5

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

With no annotations provided, the description carries full behavioral disclosure burden but only conveys that the action is on a connected local profile. It does not disclose whether the like operation is idempotent, reversible, asynchronous, or if it has side effects beyond registering a like.

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?

The description is a single, front-loaded sentence that directly states the action and scope. It is concise with no wasted words, though it omits behavioral details that could be included without much added length.

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

Completeness2/5

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

The tool has no output schema and no annotations, so the description must provide enough context for correct invocation. It only covers the basic action and connected-profile requirement, leaving out usage timing, potential asynchronous behavior, and expected outcomes, making it inadequate for a mutation tool.

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

Parameters2/5

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

Schema description coverage is 50%: only account_id is explained, while video_url is merely typed as a URI. The description adds no extra meaning about what constitutes a valid TikTok video URL or how it relates to the account, failing to compensate for the low 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 the action ('Like') and the resource ('a video from a connected local profile'), which distinguishes it from sibling tools like tiktok_follow or tiktok_post. The verb and object are specific and unambiguous.

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 explicit guidance is given on when to use this tool versus alternatives such as tiktok_follow. The description only implies usage for liking a video, with no mention of prerequisites, exclusions, or related tool choices.

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/0xArtex/tiktok-mcp'

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