Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_profile_videos

Retrieve a TikTok profile's posts newest first by handle, with max_cursor pagination to fetch older videos and options to include or exclude pinned posts.

Instructions

tiktok: Profile Videos. GET /v3/tiktok/profile/videos. Get posts from a TikTok profile, newest first, 15 per page. Follow has_more and max_cursor to page back in time. 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": {
      "handle": "<handle>"
    },
    "name": "tiktok_profile_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet to true for a trimmed down version of the response
handleYesTikTok handle
regionNoAccepted for compatibility. The US feed is read.
sort_byNolatest (the default). popular is not supported yet and returns 400.
user_idNoTikTok handle or user id. Prefer handle.
max_cursorNoCursor for the next (older) page. Use max_cursor from the previous response.
include_pinnedNoInclude pinned posts; defaults to true. false excludes them. Keep unchanged while paginating.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a solid job: it discloses result ordering, page size, the pagination contract (has_more/max_cursor), and a detailed billing model including the fact that errors, blocked/timed-out requests, invalid requests and cache hits are free. Gaps remain around rate limits, authentication, and the shape of the returned posts, but the cost and pagination behavior are genuinely useful disclosures.

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?

The purpose and pagination are front-loaded in the first two sentences, and the credit-cost sentences are informative rather than padding. The closing clause ("A not-found or empty result is charged only where that operation's published cost says so") is circular boilerplate that adds little, keeping it out of the top band.

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 7-parameter listing tool with no output schema, the description covers what matters most for correct invocation: ordering, page size, the pagination loop, and cost behavior. It omits any indication of what fields a returned post contains beyond has_more/max_cursor, which would help since no output schema exists.

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 the schema already documents trim, region, sort_by, user_id, max_cursor and include_pinned. The description adds only marginal parametric meaning, reinforcing that max_cursor walks backwards through time; it says nothing about how include_pinned should behave during pagination or what trim changes in the response.

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 gives a concrete verb and resource ("Get posts from a TikTok profile"), plus ordering ("newest first") and page size ("15 per page"), and even names the backing endpoint. It does not explicitly differentiate itself from siblings such as tiktok_profile or tiktok_search_keyword, so an agent must infer that this is the post-listing tool rather than the profile-metadata or search tool.

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?

It offers real procedural guidance for paging ("Follow has_more and max_cursor to page back in time"), which tells the agent how to iterate. However, there is no statement of when to choose this tool over the available alternatives, and no prerequisites (handle format is left to the schema). Usage is implied by the purpose rather than directed.

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