Skip to main content
Glama
Sign In
instagram-mcp-server

instagram-mcp-server

by qaassimq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Account

instagram_get_account
Read-onlyIdempotent

Retrieve the authenticated Instagram professional account profile and server capabilities, including account ID, counts, bio, website, and Meta auth features. Call first to get account ID and tools.

Instructions

Get the authenticated Instagram professional account's profile, and the server's active capabilities.

Returns username, account type, follower/following/media counts, bio and website, plus which Meta auth mode this server is running in and what that mode cannot do.

Call this first in a new session: it tells you the account ID to pass to other tools and whether hashtag search and business discovery are available at all.

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

Input Schema

NameRequiredDescriptionDefault
account_idNoInstagram professional account ID. Omit to use the account the access token belongs to, which is the normal case.
response_formatNo'markdown' for readable text, 'json' for structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds genuinely useful behavior beyond them: it discloses the auth-mode reporting and, notably, "what that mode cannot do" — a capability limitation an agent could not learn from annotations. It stops short of describing error behavior or rate-limit handling.

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?

Three sentences, front-loaded with what is returned and followed by the operational instruction. Every sentence carries distinct information — return fields, capability caveats, and call ordering — with no restatement of the tool name.

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?

With no output schema, the description carries the burden of enumerating return values, and it does so (username, account type, counts, bio, website, auth mode). It also explains the bootstrapping role for other tools. Minor gaps remain around failure modes and whether the capability report is cached per session.

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 both account_id (including the omit-to-use-token-owner default) and the response_format enum are already documented in the schema. The description adds no syntax or format detail beyond that, so baseline 3 applies even though it references the account ID's downstream use.

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 names a specific verb and resource ("Get the authenticated Instagram professional account's profile") plus a second return surface ("the server's active capabilities"). It clearly separates this from sibling tools like instagram_get_account_insights or instagram_get_audience_demographics, which read derived metrics rather than identity and capability state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit sequencing guidance: "Call this first in a new session" because it yields the account ID and reports whether hashtag search and business discovery are available. There is no stated when-not-to-use case or named alternative, but for an identity/bootstrap tool the positive guidance covers the realistic decision.

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