Skip to main content
Glama

get_audience_demographics

Read-only

Answer "who's my audience?", "where are my followers?", "what's my audience breakdown?". Returns follower demographics where the platform reports them: Instagram and Threads (country, age, gender, city) and LinkedIn company pages (seniority, job function, industry, company size, location). Other platforms (and LinkedIn member profiles) don't expose this; for those, and when nothing has been captured yet, it says so in plain text. On LinkedIn it uses the workspace's first company page that has this data. For follower counts over time, use get_follower_history.

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": {
      "platform": "<platform>"
    },
    "name": "get_audience_demographics"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoRolling window ending today. Default 30d. For any other window, pass start_date/end_date instead.
end_dateNoOptional. Last day of a custom range, YYYY-MM-DD, inclusive. Defaults to today. Needs start_date.
platformYesRequired. The network to analyze.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
start_dateNoOptional. First day of a custom range, YYYY-MM-DD, in the user's timezone. Use for windows the presets don't cover: "last 14 days", "in March", "since Jan 1", "last year". Overrides `period`. Ranges can cover up to 366 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description goes well beyond them: it discloses the LinkedIn page-selection rule (first company page with data), and that unsupported platforms or empty datasets return a plain-text explanation rather than an error or empty object. That degradation behavior is exactly the kind of thing an agent needs to interpret a response correctly.

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?

Front-loads the user-intent questions, then platform coverage, then the sibling hand-off — a sensible order for retrieval and routing. It is dense and slightly overstuffed in the middle sentence, but no sentence is disposable.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does: per-platform dimension lists, the LinkedIn page fallback, and the plain-text no-data message. For a read-only analytics tool with a fully documented 5-param schema, nothing an agent needs 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 description coverage is 100%, so the schema already documents period, start_date/end_date, platform, and workspace semantics in detail. The description adds essentially nothing parameter-level beyond platform coverage, which triggers the baseline 3.

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?

States a concrete verb+resource (follower demographics by platform) and anchors it to the actual user questions it answers ("who's my audience?", "where are my followers?"). It also enumerates the exact data dimensions per platform (Instagram/Threads country, age, gender, city; LinkedIn seniority, job function, industry, company size, location), which makes it unmistakable against siblings like get_analytics_summary or get_format_performance.

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

Usage Guidelines5/5

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

Provides explicit when-to-use and when-not-to-use: only Instagram, Threads, and LinkedIn company pages report this data, other platforms and LinkedIn member profiles do not, and follower counts over time belong to get_follower_history. The alternative is named directly, so an agent never has to guess between the two.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources