frida-ios-mcp

Overview Schema Source Related Servers Discussions Admin

tiktok_posts

Retrieve current TikTok user's posts using in-process TTNet with app signatures. Returns post details including ID, description, creation time, and share URL.

Instructions

[advanced] List current user's posts via in-process TTNet (App MetaSec signs). Returns awemeId, desc, createTime, shareUrl, stats.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tiktok_posts"
  }
}

Input Schema

Name	Required	Description
`url`	No	Override endpoint (default api.tiktokv.com/aweme/v1/aweme/post/)
`count`	No	Page size, default 12
`cursor`	No	max_cursor, default 0
`userId`	No	Override user_id if auto-detect fails

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description should fully disclose behavior. It hints at authentication ('App MetaSec signs') but lacks details on pagination behavior, error states, rate limits, or what 'advanced' implies. The description is insufficient for an agent to understand side effects or requirements.

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 description is concise (27 words) and front-loaded with the action. However, jargon like 'in-process TTNet' and 'App MetaSec signs' may reduce clarity for some agents.

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 output schema and no annotations, the description is incomplete. It mentions return fields but does not explain pagination parameters (cursor, count), how to handle errors, or prerequisites like being logged in. Essential context is missing for a list operation with pagination.

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?

All four parameters have schema descriptions (100% coverage), so baseline is 3. The description does not add significant semantic value 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?

The description clearly states the action ('List current user's posts'), the method ('via in-process TTNet (App MetaSec signs)'), and return fields. It is specific about resource and scope, but does not explicitly differentiate from sibling tools like tiktok_inbox.

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, nor any instructions on prerequisites or when not to use it.

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