Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

profile_get

Read-only

Retrieves Instagram profile details—bio and post, follower, and following counts—for a specified username or, if omitted, the signed-in account.

Instructions

Ambil info profil Instagram (bio, jumlah post/followers/following). Tanpa username = profil akun yang login.

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

Input Schema

NameRequiredDescriptionDefault
usernameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds value by disclosing the returned fields and the defaulting behavior when username is absent. It stops short of noting auth requirements or what happens for a nonexistent/private username.

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 compact sentences, front-loaded with the resource and returned fields, followed by the defaulting rule. No filler or redundancy.

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 read-only lookup with one optional parameter and annotations covering safety, this is nearly complete, and listing the returned fields compensates for the absent output schema. Only the username format and failure behavior are unaddressed.

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 0% for the single optional 'username' parameter, so the description must carry the load. It does explain the most important semantic (omitted = logged-in account), but gives no format hint (handle vs. URL vs. numeric ID), leaving ambiguity about acceptable values.

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 verb+resource ('Ambil info profil Instagram') and enumerates what is returned (bio, jumlah post/followers/following), so an agent knows exactly what it fetches. It does not explicitly distinguish itself from adjacent tools like followers_list or user_posts, keeping it short of a 5.

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 clause 'Tanpa username = profil akun yang login' tells the agent what happens when the parameter is omitted, which is a real usage rule. However, there is no guidance on when to prefer this over followers_list, following_list, or user_posts, and no exclusions or prerequisites are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.