instagram-mcp

get_profile_stats

Retrieve Instagram profile statistics by providing a username or profile URL. Access follower count, posts, and other metrics for any public profile.

Instructions

Get Instagram profile stats by username or profile URL.

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": {
      "target": "<target>"
    },
    "name": "get_profile_stats"
  }
}

Input Schema

Name	Required	Description	Default
`target`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so the description must fully disclose behavioral traits. It does not mention whether the tool is read-only, any rate limits, authentication requirements, or what happens on invalid input. The description only states the basic function.

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 a single, concise sentence without unnecessary words. It is front-loaded with the action and resource. However, it could be slightly more informative within the same length.

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?

Given the tool's simplicity (1 parameter, one-line description) and the presence of an output schema (though not provided), the description is adequate but incomplete. It does not explain what 'stats' includes, leaving the agent to infer from the output schema or context. For a tool with many siblings, more context would be beneficial.

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?

The input schema provides no description for the parameter 'target' (0% coverage). The description adds context that the target can be a username or profile URL, which helps but does not specify format, validation rules, or examples. This is a modest improvement over the schema alone.

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 clearly states the tool retrieves profile stats using a username or URL, which is a specific verb+resource. However, 'stats' is somewhat ambiguous, and the description does not differentiate it from similar profile tools like get_profile_publications, though the different resource ('stats' vs 'publications') provides some distinction.

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 is provided on when to use this tool versus the many sibling tools (e.g., get_profile_publications, get_profile_highlights). There is no mention of prerequisites, alternatives, or exclusions.

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

Deploy Server