Skip to main content
Glama

agdata

by dev.shveik
OverviewDiscussionsAdmin

TikTok videos by user, hashtag, search

tiktok
Read-only

Get TikTok videos for a username, a hashtag or a search keyword. The body is {mode: profile|hashtag|search, query, limit} and limit runs 1-20. Each video has id, url, text, created_at, author, plays, likes, comments, shares, saves, duration_s, hashtags and music; no expiring media links. raw true returns the original records. A leading @ or # in the query is stripped.

Input Schema

NameRequiredDescriptionDefault
rawNotrue returns the provider's own records instead of the compact shape
modeYesprofile=user's videos, hashtag=videos under a tag, search=keyword→videos
limitNonumber of videos wanted, 1 to 20 (default 5). A larger value is lowered to 20 and 0 or a negative one means the default; the quote follows the value used.
queryYesusername (profile), hashtag without #, or search keywords

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / raw
      Added value: +{
+  "default": false,
+  "description": "true returns the provider's own records instead of the compact shape",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds behavioral detail well beyond the annotations: 'no expiring media links' (durability of returned URLs), 'raw true returns the original records', and that a leading @ or # is stripped from the query. These are non-obvious operational traits an agent needs, and they are consistent with readOnlyHint=true.

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?

Purpose and modes are front-loaded, followed by output shape and normalization notes. The output-field list is longer but earns its place since no output schema exists; overall efficient with little wasted text.

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 fully compensates by enumerating the returned video fields and flagging the absence of expiring media links. Combined with mode, limit, raw, and normalization semantics, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by restating the body shape and, more importantly, disclosing normalize behavior (leading @ or # stripped) that the schema does not fully state, adding meaning beyond the field descriptions.

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 verb (Get) and resource (TikTok videos) and enumerates the three retrieval modes (profile, hashtag, search). The resource is clearly distinct from the sibling tiktok-comments tool, so an agent can route correctly without opening the 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?

The three modes are explained (profile=user's videos, hashtag=videos under a tag, search=keyword→videos), giving clear context for choosing among them. It does not explicitly route the agent away from or toward alternatives like tiktok-comments, so no exclusions are stated.

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

All agdata toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources