Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List TikTok trending feed

tiktok_feed_trending_list
Read-onlyIdempotent

Fetches trending TikTok posts for a specified region and returns a list, helping identify popular country-specific content for research or monitoring.

Instructions

List currently trending TikTok posts for a region. Requires region. Returns a list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_feed_trending_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoWhen true, requests a smaller response with fewer optional fields.
regionYesTwo-letter ISO 3166-1 country code for the request.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered without prose. The description adds only 'Requires `region`' and 'Returns a list', omitting anything about result volume, pagination, or authentication that would matter for a trending feed.

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 short sentences with the scope constraint front-loaded and no wasted preamble. 'Returns a list' is close to filler given there is no output schema to describe, but it costs little.

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 simple read-only list tool with full annotation coverage, the definition is serviceable, but with no output schema the agent learns nothing about what a returned item contains or how many results to expect. Given five parameters including required meta-parameters, a sentence on response shape would have closed the 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%, so all five parameters including the meta-parameters (context, llm_model, conversation_id) are documented in the schema itself. The description only echoes `region` and adds no format, default, or interplay detail beyond the schema, so baseline 3 applies.

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?

States a specific verb ('List'), resource ('trending TikTok posts'), and scope ('for a region'), so the agent knows exactly what it retrieves. The platform name separates it from the many non-TikTok trending siblings, but nothing distinguishes it from TikTok siblings like tiktok_search_top_list or tiktok_search_videos_list.

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 offers no when-to-use guidance and names no alternative. The only conditional content, 'Requires `region`', is a restatement of the schema's required field rather than routing advice.

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

Deploy Server

Other Tools