Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search TikTok videos

tiktok_search_videos_list
Read-onlyIdempotent

Search TikTok videos by free-text keyword and filter results by upload date, region, or sort order; paginate the returned list to find relevant clips.

Instructions

Search TikTok videos by free-text keyword (not hashtag — use tiktok_search_hashtag_list for that). Requires query. Returns a list (use cursor when paginated). datePosted takes yesterday, this-week, this-month, last-3-months, last-6-months or all-time.

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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_search_videos_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoWhen true, returns a smaller response with fewer fields.
queryYesRequired. Search query text for TikTok videos.
cursorNoOpaque pagination cursor returned by a previous response.
regionNoOptional two-letter ISO 3166-1 country code for localized search results.
sortByNoOptional sort order for search results.
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.
datePostedNoOptional upload date filter for video results.
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. Beyond that, the description adds return shape ('Returns a list') and pagination behavior ('use cursor when paginated'), which the annotations do not convey. It omits the notable sequencing constraint on conversation_id, but that constraint is fully spelled out in the schema.

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?

Four short sentences with the primary scope and the sibling exclusion front-loaded, then the required-parameter reminder and return behavior. The 'Requires query' sentence is redundant with the schema's required list, but nothing else is padding.

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?

For a 9-parameter search tool with no output schema, the description covers scope, return shape and pagination, which is the information an agent cannot get from annotations. The three required parameters and the conversation_id handshake are handled entirely by the schema, which is fully documented, so nothing critical is missing.

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 every parameter is already documented, and the description largely restates it: 'Requires query' and the datePosted enum values duplicate the schema verbatim. It adds no syntax, default or interaction detail beyond the structured fields, 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?

States a specific verb and resource ('Search TikTok videos by free-text keyword') and immediately contrasts the scope against the sibling 'tiktok_search_hashtag_list'. An agent can distinguish keyword search from hashtag search without opening 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 an explicit when-not rule with the named alternative for hashtag searches, which is the most likely confusion point among the siblings. It does not address other plausible alternatives such as tiktok_search_top_list, tiktok_search_suggestions_list or tiktok_users_search, so the routing guidance is clear but not exhaustive.

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