Socify-mcp

tiktok_profile/following

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

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: +[
+  "ishowspeed"
+]
```
AddedNov 3, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description does carry some real behavioral weight: it discloses the per-request cost of 1 credit and the Bearer auth requirement, which are useful operational facts. However it says nothing about rate limits, cursor expiry, result ordering, or what a page contains, leaving the read-only/mutation profile undeclared.

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?

Very short and front-loaded with the purpose, with metadata (platform, resource, cost, auth) following in a predictable pattern. Minor typographic noise (double period) and boilerplate key=value fragments keep it from a 5.

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 two-parameter paginated read with a fully documented schema and no output schema, the description covers purpose, cost, and auth, which is most of what an agent needs to call it correctly. It could still say more about the page size or what happens at the end of the list.

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 coverage is 100%, and both parameters (username without @, cursor from a previous response) are fully documented in the schema, so the baseline applies. The description adds no syntax or format detail beyond what the schema already provides.

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?

"Fetch a page of accounts a username follows" gives a specific verb (fetch), resource (accounts a user follows), and scope (a page). It is clearly distinguishable from tiktok_profile/followers by the word "follows", though the description never names that sibling explicitly.

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 only implied by the tool's name and the word "page" – an agent can infer pagination via the cursor, but there is no explicit statement of when to use this versus tiktok_profile/followers or tiktok_profile/info, and no prerequisites or limits are given.

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?