Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Look up public account

instagram_lookup_account
Read-onlyIdempotent

Retrieve public profile stats and recent media for another Instagram business or creator account by username to support competitor and partner research.

Instructions

Business discovery: public profile stats and recent media of another Instagram business/creator account by username. Facebook login path only (instagram login path returns CAPABILITY_UNAVAILABLE).

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": {
      "username": "<username>"
    },
    "name": "instagram_lookup_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.
usernameYesUsername to look up (leading @ allowed).
media_limitNoRecent media to include (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavior: it only works on the Facebook login path and returns CAPABILITY_UNAVAILABLE on the Instagram login path. It also signals the public/business-only restriction on the target account, though it says nothing about rate limits or private-account failures.

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 tight sentences with zero filler: the capability is stated first, then the hard operational constraint. Nothing in the text is redundant with the title or wasteful.

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 simple three-parameter read tool with no output schema, the description names what comes back (profile stats and recent media), the target type, and the login-path limitation. It could go slightly further on failure modes for non-business or private accounts, but the essentials for correct invocation are present.

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 three parameters (account, username, media_limit) are already documented including defaults and bounds. The description adds only loose framing ('by username', 'recent media') and no new syntax, format, or edge-case meaning beyond the schema.

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?

States a specific operation (business discovery lookup) and resource (public profile stats plus recent media) scoped to another Instagram business/creator account by username. The contrast with the caller's own account is implied by 'another ... account', which distinguishes it from instagram_get_profile and instagram_get_media, though those siblings are never named.

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 target scope ('another Instagram business/creator account', 'public profile') and the Facebook-login precondition imply when the tool applies. However, no explicit alternatives are named (e.g. instagram_compare_accounts, instagram_get_audience, instagram_search_hashtag), and there is no guidance on when not to use it.

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