Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok profile

tiktok_profile_get
Read-onlyIdempotent

Retrieve a TikTok profile by handle to get follower counts, post totals, private account status, and account creation date.

Instructions

Get a TikTok profile by handle. Requires handle. Returns lookupStatus plus profile metrics (followers, posts/videoCount, privateAccount, accountCreatedAt).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_profile_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. TikTok handle to look up, with or without a leading @.
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. The description adds the notion of a 'lookupStatus' result and enumerates returned metrics, but says nothing about failure modes (e.g., unknown handle), rate limits, or cache/freshness behavior for an open-world lookup.

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, front-loaded with the action and the required parameter. No filler, though the return-fields enumeration slightly crowds what is otherwise a tight definition.

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?

No output schema exists, so listing the returned fields (lookupStatus, followers, videoCount, privateAccount, accountCreatedAt) genuinely compensates. What remains missing is minor: the meaning of lookupStatus values and handling of non-existent handles.

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 handle, context, llm_model, and conversation_id are already documented in detail. The description only repeats that handle is required, adding no syntax or format meaning beyond the schema.

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 and resource: 'Get a TikTok profile by handle.' The scope (single profile lookup by handle) implicitly separates it from the metric/list siblings (audience, engagement, region, followers_list), though no sibling is named explicitly.

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?

Only states the precondition 'Requires `handle`'. There is no guidance on when to use this vs tiktok_profile_audience_get, tiktok_profile_engagement_get, or tiktok_profile_region_get, nor any exclusions or error conditions.

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