Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_profile

Fetch a public TikTok profile by handle or user ID to retrieve account details and profile statistics.

Instructions

tiktok: Profile. GET /v1/tiktok/profile. Scrapes a public TikTok profile Costs 1 credit when it succeeds. Costs 1 credit when the outcome is absent. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiktok_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoTikTok handle. You can pass handle or user_id.
user_idNoTikTok user id.
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so for billing: it explains exactly what is charged on success, on absent outcomes, and what is free (errors, blocked, timeouts, invalid requests, cache hits). It does not cover authentication needs, rate limits, or what the profile payload contains, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and endpoint are front-loaded, which is good, but the pricing text is bloated and partly self-referential: 'Costs 1 credit when the outcome is absent' and 'charged only where that operation's published cost says so' say similar things and push the agent toward circular reasoning. It could be condensed to one or two sentences without losing information.

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 read-only scraping tool with no annotations and no output schema, the definition covers identity, endpoint, and cost model thoroughly enough to call safely. The main missing piece is any indication of what fields the returned profile includes, which the absent output schema would otherwise have supplied.

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 coverage is 100%, so handle, user_id and cache_max_age are already documented in the schema; the description adds only the link between cache hits and zero cost. That is a small but real complement to the cache_max_age parameter, consistent with the baseline 3 for fully documented schemas.

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 concrete verb and resource ('Scrapes a public TikTok profile') plus the underlying endpoint GET /v1/tiktok/profile, which is far more specific than the bare name. It does not explicitly distinguish itself from the many sibling profile tools (instagram_profile, tiktok_user_followers, etc.), so it stops short of 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 Guidelines2/5

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

There is no guidance on when to call this versus alternatives such as tiktok_user_followers or tiktok_profile_videos, and no prerequisites are stated. The word 'public' hints at a scope limit, but the agent must infer it.

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