Skip to main content
Glama
Sign In

HasData

by com.hasdata
OverviewDiscussionsAdmin

tiktok_profile: GET /

hasdata_tiktok_profile_getTikTokProfile
Read-only

Get TikTok Profile

Fetches a public TikTok profile by username (handle) and returns nickname, biography, bio link, avatar URLs, verified/private flags, account creation time, and followers, follows, likes, videos, and friends counts. Use to enrich CRM/lead records, verify influencer reach before outreach, monitor competitor accounts, or build datasets of creator metadata for vetting and analytics.

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": "hasdata_tiktok_profile_getTikTokProfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe TikTok username of the profile you want to scrape, with or without the `@` symbol.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the meaningful constraint that only public profiles are fetched and discloses the returned data surface, though it says nothing about auth needs, rate limits, or behavior on missing/private handles.

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?

Front-loaded with the core action before the return list and use cases. Minor redundancy between the title restatement "Get TikTok Profile" and the opening sentence, and the four-item use-case list is slightly long but each item is substantive.

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 single-parameter read tool with no output schema, the description compensates by enumerating the returned fields and the intended use cases. It is nearly complete; only error/empty-profile behavior and rate-limit context are absent, which is a minor gap.

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% and the single handle parameter is fully documented there, including the optional `@` prefix. The description only restates "by username (handle)" and adds no format or normalization detail beyond the schema, so 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?

Opens with a specific verb and resource ("Fetches a public TikTok profile by username") and enumerates the exact return set (nickname, bio, avatar URLs, flags, counts). An agent can distinguish this from hasdata_instagram_profile_getInstagramProfile or hasdata_facebook_profile_getFacebookProfile on platform and data shape alone.

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 concrete usage contexts — CRM/lead enrichment, influencer vetting before outreach, competitor monitoring, dataset building — which orients the agent well. It stops short of naming sibling tools or stating when NOT to use it (e.g. vs tiktok_posts or tiktok_search), so it is clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HasData toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources