Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Compare accounts

instagram_compare_accounts
Read-onlyIdempotent

Compare your Instagram account with up to 10 public business or creator accounts on followers, posting cadence, average likes/comments, and format mix using a recent post sample.

Instructions

Compare your account with up to 10 other public business/creator accounts: followers, posting cadence, average likes/comments and format mix over a recent sample. Facebook login path only.

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": {
      "usernames": "<usernames>"
    },
    "name": "instagram_compare_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.
usernamesYes
media_limitNoPosts sampled per account (default 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, and open-world behavior. The description adds meaningful constraints beyond that: accounts must be public business/creator accounts, the comparison is capped at 10 accounts, metrics come from a recent sample, and only the Facebook login path is supported.

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 tightly written sentences front-load the comparison scope and metrics, then add the login-path constraint. There is no filler and the most important eligibility information arrives early.

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 comparison tool with no output schema, the description covers the compared metrics, account eligibility, maximum comparison set, sample nature, and login constraint. Minor gaps remain around exact sampling period and behavior for private or ineligible accounts, but the core call requirements are clear.

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?

Schema coverage is 67%, with account and media_limit documented in the schema. The description adds semantic meaning for usernames by restricting them to public business/creator accounts and reinforces the 10-account cap; it also contextualizes media_limit as the basis for a 'recent sample.' The account alias parameter remains only schema-documented.

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?

The description uses a specific verb and resource ('Compare your account with up to 10 other public business/creator accounts') and names the exact metrics compared: followers, posting cadence, average likes/comments, and format mix. It clearly differs from single-account siblings such as instagram_get_account_insights or instagram_get_profile.

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?

Usage is implied: benchmark your account against other public business/creator accounts. The 'Facebook login path only' constraint is helpful, but no alternative tools are named and there is no explicit when-not-to-use guidance versus instagram_get_account_insights or instagram_get_audience.

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