Skip to main content
Glama
olamide-olaniyan

SociaVault MCP Server

get_tiktok_profile

Retrieve TikTok profile data by username to access user information and metrics through the SociaVault MCP Server.

Instructions

Get TikTok profile data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleYesTikTok username

Implementation Reference

  • Handler for the get_tiktok_profile tool: makes API call to Sociavault TikTok profile endpoint and extracts data using extractTikTokProfile helper.
    if (name === "get_tiktok_profile") {
      const { handle } = args as { handle: string };
      const response = await axios.get(`${BASE_URL}/tiktok/profile`, {
        headers: { "X-API-Key": API_KEY },
        params: { handle },
      });
      const extracted = extractTikTokProfile(response.data);
      return {
        content: [{ type: "text", text: JSON.stringify(extracted, null, 2) }],
      };
    }
  • src/index.ts:223-233 (registration)
    Registration of the get_tiktok_profile tool in the tools array, including name, description, and input schema.
    {
      name: "get_tiktok_profile",
      description: "Get TikTok profile data",
      inputSchema: {
        type: "object",
        properties: {
          handle: { type: "string", description: "TikTok username" },
        },
        required: ["handle"],
      },
    },
  • Helper function to extract structured TikTok profile data from the API response.
    function extractTikTokProfile(data: any) {
      const user = data?.data?.userInfo?.user || data?.user || {};
      const stats = data?.data?.userInfo?.stats || user.stats || {};
      return {
        username: user.uniqueId || user.username,
        nickname: user.nickname,
        signature: user.signature,
        followers: stats.followerCount || 0,
        following: stats.followingCount || 0,
        likes: stats.heartCount || stats.heart || 0,
        videos: stats.videoCount || 0,
        verified: user.verified,
        avatar: user.avatarLarger || user.avatarMedium,
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets' data, implying a read-only operation, but doesn't specify authentication needs, rate limits, error conditions, or what the return data looks like (e.g., JSON structure). This is a significant gap for a tool with no annotation coverage.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's front-loaded and appropriately sized for a simple tool, earning full marks for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what profile data is returned (e.g., bio, follower count), potential errors, or behavioral traits. For a tool with no structured support, this leaves critical gaps for an AI agent.

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?

The input schema has 100% description coverage, with the 'handle' parameter documented as 'TikTok username'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get TikTok profile data' clearly states the action (get) and resource (TikTok profile data), but it's vague about what specific data is retrieved and doesn't distinguish it from sibling tools like get_tiktok_videos. It's a minimal but functional purpose statement.

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?

The description provides no guidance on when to use this tool versus alternatives like get_tiktok_videos or other profile tools (e.g., get_instagram_profile). There's no mention of prerequisites, context, or exclusions, leaving usage entirely implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/olamide-olaniyan/sociavault-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server