Hosted TikTok Pages MCP server, with each action switched on or off per account.
Scored across 4 tools
execute_action and query_data are especially hard to distinguish: both are labeled 'Step 3 (FINAL) of workflow' and both require the exact same query_contexts prerequisites. Without clearer separation between mutation actions and data reads, an agent may misselect between them.
Three tools follow a verb_noun pattern (execute_action, query_contexts, query_data), but prompts_menu breaks the pattern and reads as a noun phrase. The set is still readable, but the convention is mixed.
Four tools is a compact, mostly well-scoped set for this workflow-oriented server. The count is reasonable, though the auxiliary planning/prompt tools add some surface without expanding core capability.
The core workflow is covered through context discovery, querying, and action execution, but prompt handling is browse-only and there is no visible tooling for creating or updating prompts. Account/brand operations also appear only indirectly through query_contexts, leaving some lifecycle gaps.
Execute TikTok Profile action (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id, account_id AND available_actions
request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions
IMPORTANT: Always call step 2 to see the exact body structure before executing.
Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.
Inputs: body (required). Returns: object
Helper for planning InsightfulPipe TikTok Profile data queries.
Step 1: request='accounts' – Retrieve workspace_id, brand_id, account_id, other source metadata, AND available_actions (all tables you can query).
Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.
Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).
Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.
Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object
Query TikTok Profile data (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id, account_id AND available_actions
request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions
IMPORTANT: Always call step 2 to see the exact body structure before querying.
Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.
Inputs: body (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Hosted Facebook Pages MCP server, with each action switched on or off per account.
Hosted Snapchat Ads MCP server, with each action switched on or off per account.
Hosted Pinterest Pages MCP server, with each action switched on or off per account.
Hosted TikTok Ads MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Add one secure layer between your agents and this server.