Instagram MCP Server

Get Activity Insights

get_activity_insights

Read-only

Retrieve profile activity insights from Instagram Professional Dashboard for Business and Creator accounts. Specify a time range (7d, 30d, 90d) to get actionable data.

Instructions

Get profile activity insights from Professional Dashboard.

Note: Professional Dashboard is only available for Business and Creator accounts.

Args: ctx: FastMCP context for progress reporting time_range: Time range for insights data (7d, 30d, 90d). Default: "7d"

Returns: Dict with url, sections (name -> raw text), and optional references. The LLM should parse the raw text to extract profile activity data.

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": "get_activity_insights"
  }
}

Input Schema

Name	Required	Description	Default
`time_range`	No		7d

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior4/5

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

The description discloses important behavioral traits beyond the readOnlyHint annotation: it explains the return format (Dict with url, sections as raw text) and instructs the LLM to parse the raw text. It also adds the account availability restriction. This goes beyond what annotations provide, earning a solid score.

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?

The description is well-structured with separate sections for args and returns, and the availability note is prominently placed. It is concise but loses a point due to the unnecessary mention of 'ctx' which adds noise and potential confusion.

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?

For a tool with one parameter and an output schema, the description covers the essential return format and parsing expectation. However, it does not clarify what 'profile activity insights' actually contain, nor does it help the agent choose this over related insights tools. It is adequate but leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description enriches the only schema parameter 'time_range' by specifying allowed values (7d, 30d, 90d) and a default. However, it also documents 'ctx' as an argument, which is not present in the input schema (and additionalProperties is false). This is misleading and contradicts the schema, so the parameter guidance is partially unreliable.

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?

The description states a specific verb and resource: 'Get profile activity insights from Professional Dashboard.' This clearly indicates what the tool does. However, it does not distinguish it from sibling tools like get_business_insights or get_content_insights, which might also provide insight-related data, so it misses the opportunity to differentiate.

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 note 'Professional Dashboard is only available for Business and Creator accounts' provides a clear prerequisite and limits when the tool should be used. Yet, it does not explicitly say when to prefer this tool over alternatives or mention any exclusions, so the guidance is only partly useful.

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