Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get profile

instagram_get_profile
Read-onlyIdempotent

Retrieve the connected Instagram account's profile details, including username, bio, website, follower counts, profile picture URL, and account type.

Instructions

Profile of the connected account: username, name, bio, website, counts, profile picture URL and account type. On the facebook and unified login paths account_type is always null and warnings says so (the Graph API does not provide it there).

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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), so the description's real contribution is the caveat that account_type is always null on the facebook and unified login paths and that this is surfaced via a 'warnings' field. That is genuinely useful behavior an agent could not learn from the annotations or schema, and it implicitly reveals a warnings element in the response. It stops short of describing the rest of the return shape.

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?

Two tight sentences: the field inventory is front-loaded and the login-path caveat follows. Every clause carries information; only the parenthetical explanation of why the Graph API behaves this way is mildly optional.

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?

There is no output schema, so the description correctly spends its words enumerating the returned fields and flagging the one field that can be null. For a single-parameter read tool this is close to complete; a brief note on selecting the account alias would have closed the remaining gap.

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?

With a single parameter at 100% schema coverage, the schema already explains that 'account' is an alias defaulting to the configured default. The description adds nothing about the parameter, which is acceptable given the baseline but leaves no extra value.

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 resource (the connected account's profile) and enumerates the returned fields: username, name, bio, website, counts, picture URL, account type. The phrase 'connected account' implicitly separates it from siblings like instagram_lookup_account or instagram_list_accounts, but it never names an alternative explicitly.

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 only implied: an agent can infer this is the tool for reading the currently authenticated account's own profile rather than someone else's. There is no explicit when-to-use/when-not or routing to instagram_lookup_account for other accounts, and no mention of prerequisites such as which login path is active.

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