Socify-mcp

tiktok_profile/info

Fetch a public TikTok profile by username: bio, stats, verification, and avatar.. Platform=tiktok resource=profile/info. Costs 1 credit(s) per request. Requires Authorization: Bearer <api_key>.

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": {
      "username": "<username>"
    },
    "name": "tiktok_profile/info"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	TikTok username without @.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- changedInput schema / properties / username / examples
```
Previous value: -[
-  "daviddobrik"
-]New value: +[
+  "mrbeast"
+]
```
AddedNov 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real context beyond the schema: the operation is read-only in nature ('Fetch'), limited to public profiles, costs 1 credit per request, and needs a Bearer API key. It omits failure modes (private or deleted accounts), rate limits, and pagination/response shape, which are the more consequential gaps for an unannotated tool.

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 value proposition is front-loaded in the first clause, and the total length is short. Minor waste: a double period after 'avatar..' and a 'Platform=tiktok resource=profile/info' fragment that duplicates information already encoded in the tool name.

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 one-parameter lookup with no output schema, the description covers the essentials an agent needs: what identifier to supply, which fields come back, what it costs, and what auth is required. Remaining gaps are error/edge-case behavior for private or missing accounts, which would be nice but are not blocking for a simple read.

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?

There is a single parameter with 100% schema description coverage, including the crucial '@'-less format and an example, so the schema already does the heavy lifting. The description's 'by username' merely restates the parameter and adds no format or validation detail beyond what is structured.

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 specific verb+resource ('Fetch a public TikTok profile by username') and enumerates the returned fields (bio, stats, verification, avatar), which is far more informative than the raw name. It does not explicitly contrast with sibling endpoints like tiktok_profile/videos or tiktok_profile/followers, but the resource path is specific enough that an agent can tell them apart.

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?

Usage is implied by 'by username' and the 'public' qualifier, so an agent knows to use it when it has a handle rather than a user ID. However, there is no explicit when-to-use guidance, no statement about what happens for private/nonexistent accounts, and no routing to sibling endpoints for videos, followers, or following.

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

All Socify-mcp tools Inspect

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

Need Help?