Threads MCP

Who follows this profile

get_follower_demographics

Read-onlyIdempotent

Get Threads follower demographics by country, city, age, or gender. Select one breakdown per call to analyze audience composition; requires at least 100 followers.

Instructions

Follower breakdown by country, city, age or gender. One dimension per call: Threads refuses more than one breakdown at a time. Needs at least 100 followers, and ignores any date range.

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": {
      "breakdown": "<breakdown>"
    },
    "name": "get_follower_demographics"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No	Which connected Threads profile to act as, by username (for example 'thenavidm'). Defaults to the first connected profile. Call list_accounts to see them.
`breakdown`	Yes	Which dimension to break followers down by. Only one per call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds meaningful behavioral constraints beyond those annotations: Threads rejects multiple breakdowns per call, at least 100 followers are required, and any provided date range is ignored. This is exactly the kind of contextual behavior an agent needs.

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

Conciseness5/5

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

Three short sentences deliver all key facts with no filler. The core purpose is front-loaded, and each additional sentence adds a distinct operational constraint.

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

Completeness5/5

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

For a read-only, single-dimension demographic breakdown tool, the description covers what the tool does, the key constraint, the minimum follower threshold, and the date-range caveat. The schema covers parameter details, and no output schema is expected for invocation. Nothing critical is missing.

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%, so the schema already documents both parameters. The description's mention of dimensions and the one-per-call rule largely duplicates the schema's enum and description, adding little semantic value beyond what is already structured.

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

Purpose5/5

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

The description clearly states what the tool does: provides a follower breakdown by country, city, age, or gender. It is easily distinguished from siblings like get_account_insights and get_post_insights because it is specifically about follower demographics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete usage context: one dimension per call, a 100-follower minimum, and that date ranges are ignored. It does not explicitly name alternative tools or state when not to use it, but the constraints are clear and actionable.

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