Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get audience

instagram_get_audience
Read-onlyIdempotent

Retrieve Instagram follower demographics (age, gender, city, country) and online-follower activity by hour to understand who your audience is and when they are active.

Instructions

Follower and engaged-audience demographics (age, gender, city, country) plus online followers by hour when Meta provides them. Engaged and online sections are best-effort: failures are listed in "unavailable", never fatal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "instagram_get_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.
timeframeNoDefault this_month.
breakdownsNoDefault all four.
include_engagedNoDefault true.
include_online_followersNoDefault true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds real value beyond them: it discloses that engaged and online-follower sections are best-effort and that failures appear in an "unavailable" field rather than causing fatal errors — behavior an agent could not infer from schema or annotations. It does not mention permission requirements or rate limits, keeping it short of a 5.

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?

Two sentences, no filler, front-loaded with what is returned and followed by the reliability caveat. Every sentence carries information an agent needs.

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

Completeness4/5

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

For a read-only, zero-required-parameter reporting tool with a fully described schema and no output schema, the description covers what data is returned and how partial failures surface. Slightly short of complete because the shape of the returned data (and the contents of "unavailable") is only named, not characterized, and no output schema exists to compensate.

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 five parameters (account, timeframe, breakdowns, include_engaged, include_online_followers) are already documented with defaults and enums. The description adds only the semantic link between the include_engaged/include_online_followers flags and the best-effort failure mode, which is modest supplemental meaning. Baseline 3 is appropriate.

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 specific resource (follower and engaged-audience demographics: age, gender, city, country) plus online followers by hour, which clearly separates it from siblings like instagram_get_account_insights, instagram_get_media_insights, and instagram_get_growth.

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

Usage Guidelines3/5

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

The description implies when the tool is useful (audience demographics), but never names alternatives such as instagram_get_account_insights or instagram_get_growth, and gives no explicit when-not guidance. It does state defaults for engaged/online sections indirectly through the best-effort framing, which helps an agent decide whether to enable those flags.

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