Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get TikTok profile audience

tiktok_profile_audience_get
Read-onlyIdempotent

Retrieve audience location demographics for a TikTok profile by handle to identify where its viewers are located.

Instructions

Get audience location demographics for a TikTok profile by handle. 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_audience_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.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that: no mention of rate limits, auth requirements, granularity of the demographic breakdown, or how results are scoped, leaving behavior undocumented beyond the annotation set.

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?

Two short sentences, front-loaded with the purpose, with no filler. The second sentence ('Requires `handle`') is largely redundant with the schema's required list, which is the only minor waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description could have described the shape of the returned demographic breakdown (e.g. country/city tiers). For a simple read-only lookup the current text is minimally sufficient, but it leaves the return content and its granularity unspecified.

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 all four parameters (including the unusual context, llm_model, and conversation_id) are already fully documented in the schema. The description only repeats that `handle` is required, adding no syntax or format meaning beyond what is structured. Baseline 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: 'Get audience location demographics for a TikTok profile by handle.' The scope is concrete, but it does not distinguish itself from the similarly named sibling tiktok_profile_region_get, which an agent could easily confuse with audience-location demographics.

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 only guidance is 'Requires `handle`', which is a prerequisite rather than a when-to-use rule. There is no statement of when this tool is preferable to tiktok_profile_get or tiktok_profile_region_get, and no exclusions or conditions.

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