Skip to main content
Glama

tiktok_feed

Collect video metadata from TikTok's For You Page to analyze trending content and user engagement patterns.

Instructions

Scroll the For You Page like a real user and collect video metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of videos to collect (default 10)

Implementation Reference

  • The `tiktok_feed` tool is handled in the `call_tool` function by invoking `browser.scroll_feed`. It is handled together with `tiktok_trending`.
    elif name == "tiktok_trending" or name == "tiktok_feed":
        results = await browser.scroll_feed(arguments.get("count", 20))
        return [TextContent(type="text", text=json.dumps(results, indent=2, ensure_ascii=False))]
  • The `tiktok_feed` tool schema is defined in the `TOOLS` list, specifying the `count` parameter.
    Tool(
        name="tiktok_feed",
        description="Scroll the For You Page like a real user and collect video metadata.",
        inputSchema={
            "type": "object",
            "properties": {
                "count": {"type": "integer", "description": "Number of videos to collect (default 10)", "default": 10},
            },
        },
    ),
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'like a real user,' hinting at realistic behavior, but lacks details on rate limits, authentication needs, data freshness, or potential side effects (e.g., if scrolling affects user sessions). This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that directly states the action and outcome without unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured.

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?

Given the complexity of simulating user scrolling and collecting metadata, with no annotations and no output schema, the description is insufficient. It doesn't explain what 'video metadata' includes, how data is returned, or any constraints like pagination or errors, leaving the agent with incomplete context for effective use.

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?

The schema description coverage is 100%, with the parameter 'count' well-documented in the schema. The description adds no additional parameter semantics beyond implying collection of video metadata, which is already covered by the tool's purpose. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Scroll the For You Page') and the outcome ('collect video metadata'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from siblings like 'tiktok_trending' or 'tiktok_search', which might also collect video metadata in different contexts, so it's not a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'tiktok_trending' (likely for trending videos) and 'tiktok_search' (for search-based collection), there's no indication of when this tool is preferred, such as for personalized feeds or real-time scrolling.

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

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