Skip to main content
Glama
Sign In
Instagram MCP

Instagram MCP

by nelsonrogers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Instagram profile

get_instagram_profile
Read-onlyIdempotent

Retrieve the connected Instagram account's profile details and current counts—username, display name, biography, website, followers, following, and posts—for account overviews and audience analysis.

Instructions

The connected Instagram account's profile and current counts: username, display name, biography, website, followers, following and number of posts. For performance over a period use get_instagram_performance_summary.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the meaningful behavioral fact that results reflect the connected account and are a current snapshot of counts, which matters for interpreting the numbers; it does not discuss auth failures or rate limits.

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 sentences, both front-loaded: what you get first, the alternative second. No filler, no restating the tool title, and every clause carries content.

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?

Zero parameters, a full output schema and rich annotations mean little more is required, and the description covers scope and sibling routing. It stops short of noting prerequisites such as the account needing to be connected/authenticated, which is the one operational gap.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate and the baseline applies. The description instead spends its words on output fields, which is the useful information here.

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?

States a specific verb+resource ('the connected Instagram account's profile') and enumerates the returned fields: username, display name, biography, website, followers, following, post count. The 'connected account' qualifier also separates it from the public-account sibling.

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?

Explicitly routes the agent to get_instagram_performance_summary when the need is 'performance over a period', giving a concrete condition for the alternative. It does not state exclusions against other profile-adjacent siblings (e.g. auth status), so it is clear but not exhaustive.

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