Socify-mcp

tiktok_profile/followers

Fetch a page of followers for a username.. Platform=tiktok resource=profile/followers. 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/followers"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	Pagination cursor from a previous response.
`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: -[
-  "lilyachty"
-]New value: +[
+  "mrbeast"
+]
```
AddedNov 3, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description does carry useful non-schema context: it discloses the per-request credit cost and the required Bearer auth header, and 'a page of' signals pagination. However, it says nothing about what follower data is returned, page size limits, or error behavior for private/nonexistent accounts, leaving real gaps for a read tool with zero 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.

Conciseness4/5

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

Three short, front-loaded sentences that each add something (purpose, cost, auth). Minor blemish: the stray double period after 'username..' and a slightly mechanical metadata style, but nothing extraneous.

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 simple two-parameter read tool with full schema coverage and no output schema, the description covers purpose, cost, and auth adequately. The main missing piece is any hint about the shape or volume of returned follower records, which matters somewhat given no output schema exists.

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 both parameters are documented there, including the 'without @' nuance for username and the cursor's origin. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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 ('Fetch a page of followers for a username'), and the path 'profile/followers' plus sibling 'tiktok_profile/following' make the followers-vs-following distinction inferable. It stops short of explicitly contrasting itself with the sibling, so it is clear but not fully differentiated in prose.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the sibling tools an agent might choose instead (e.g. tiktok_profile/info or tiktok_profile/following). Usage must be inferred purely from the tool name and path.

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?