Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_get_trending_feed

Fetch the TikTok trending feed for a specified region, with an optional trimmed response. Use it to retrieve TikTok feed data through the Fetchproof API.

Instructions

tiktok: Trending Feed. GET /v1/tiktok/get-trending-feed. Get the trending feed from TikTok. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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>"
    },
    "name": "tiktok_get_trending_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet to true to get a trimmed response.
regionYesAccepted for compatibility. The anonymous US For You feed is read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add genuine behavioral context that structured fields do not: a 1-credit charge only on success, no charge for errors, blocked, timed-out or invalid requests, free cache hits (revealing that responses may be cached), and conditional charging on empty/not-found results. What is missing is the response shape, any rate limit or auth expectation, and how many items the feed returns.

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 sentences, front-loaded with the resource and route, then the billing rules. The cost sentence has a slightly boilerplate, templated feel ('A not-found or empty result is charged only where that operation's published cost says so'), but each sentence carries information an agent needs to avoid surprise charges.

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?

With no annotations and no output schema, the description is the only source of behavioral information, and it covers cost but not returns. An agent still does not know what a trending-feed item contains (video metadata? author? counts?) or whether pagination/limits apply, which matters for a feed endpoint; the region-compatibility quirk lives only in the schema, not the description.

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 both 'trim' and 'region' are already documented in the input schema, including the notable caveat that region is accepted for compatibility while the anonymous US For You feed is read. The description adds no parameter-level meaning of its own, so the baseline of 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?

The description pairs a specific verb with a specific resource ('Get the trending feed from TikTok') and even names the backing route GET /v1/tiktok/get-trending-feed, so an agent can immediately tell this is a read of TikTok's trending feed rather than a profile, search, or video-detail call. It stops short of naming a sibling (e.g. tiktok_search_keyword or instagram_reels_trending) as the alternative, so it does not fully earn a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the word 'trending': an agent can infer this is the entry point for discovering popular TikTok content, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative when a targeted search or the profile feed is more appropriate. The cost sentences give some decision-relevant context (cheap on cache hits), but not routing guidance.

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