Skip to main content
Glama

ig_get_account_insights

Retrieve Instagram account performance metrics including views, reach, follower count, reposts, accounts engaged, and total interactions. Specify period and date range to analyze audience growth and engagement trends.

Instructions

Get Instagram account insights. Note: 'impressions', 'email_contacts', 'phone_call_clicks', 'text_message_clicks', 'get_directions_clicks', 'website_clicks', 'profile_views' were deprecated in v22.0. Use 'views', 'reach', 'follower_count', 'reposts' instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricYesComma-separated metrics: views,reach,follower_count,reposts,accounts_engaged,total_interactions
periodYesAggregation period
sinceNoStart date (Unix timestamp or ISO 8601)
untilNoEnd date (Unix timestamp or ISO 8601)
Behavior2/5

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

No annotations provided, so the description bears full responsibility. It fails to disclose behavioral traits like authentication requirements, rate limits, or the read-only nature of insights. The deprecation note is helpful but insufficient.

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 concise: one sentence for purpose plus a clear note on deprecations. It is front-loaded with the main function. Minor improvement could be separating the note into bullet points for clarity.

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?

Adequate for a tool with well-documented schema and deprecation context, but lacks any mention of return values or output structure, which would help the agent interpret results. No output schema exists, so description should compensate.

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

Parameters4/5

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

Input schema covers all 4 parameters with descriptions (100% coverage). The description adds value by listing deprecated metrics and their replacements, which is not in the schema, helping the agent choose valid metrics.

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 'Get Instagram account insights' with a clear verb and resource. It also mentions deprecated metrics and their replacements, adding specificity. However, it does not explicitly differentiate from sibling tools like ig_get_media_insights, though the name implies account-level insights.

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?

No guidance on when to use this tool versus alternatives. The description only notes deprecated metrics, not context or prerequisites for appropriate usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/meta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server