Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok profile engagement audit

tiktok_profile_engagement_get
Read-onlyIdempotent

Retrieve a TikTok profile engagement audit by handle to assess audience interaction and content performance.

Instructions

Get TikTok profile engagement audit. Requires handle.

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "tiktok_profile_engagement_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. TikTok handle to look up, with or without a leading @.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no mention of what the audit returns, whether it hits live external data with rate limits, or how freshness/idempotency manifests across calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Two short front-loaded sentences with no filler, so there is no verbosity problem. However, the brevity stems from under-specification rather than economy — the second sentence delays nothing and the first only echoes the title.

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?

With no output schema and a domain concept ("engagement audit") that is undefined, the description leaves the agent unable to predict the response shape or decide between this and the other TikTok profile tools. For a read-only analytics lookup against many close siblings, more routing and return-content context is warranted.

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%, so every parameter including the contextual ones (`context`, `llm_model`, `conversation_id`) is already documented in the schema. The description's "Requires `handle`" only repeats what the schema marks as required, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get TikTok profile engagement audit" essentially restates the tool name and title verbatim, adding no further specificity. It does identify the resource (TikTok profile) and a verb (get), but an agent learns nothing about what an "engagement audit" contains or how it differs from siblings like tiktok_profile_get or tiktok_profile_audience_get.

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 when-to-use guidance, no when-not-to-use, and no named alternative among the many sibling tools. The only guidance is "Requires `handle`," which is a prerequisite already fully expressed in the schema, not a usage rule.

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

Deploy Server

Other Tools