Skip to main content
Glama

Instagram Profile

instagram_profile
Read-only

Fetch public profile information from Instagram. Returns bio, follower/following counts, post count, list of posts, verification status, and profile links.

Each listed post's id is its shortcode; pass it to instagram_post for the full post, reel, or carousel details.

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

Input Schema

NameRequiredDescriptionDefault
usernameYesInstagram username (without @). Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint true), so the description only needs to add context — and it does by enumerating the returned fields, which substitutes for the absent output schema. The word 'public' hints at the private-account limitation but never spells out failure behavior 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 tight paragraphs: the capability and return payload first, then the chaining hint. Every sentence carries information useful for invocation; nothing is repeated from the schema or annotations.

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's field enumeration is essential and present, and the sibling chaining is explained. It stops short of describing error or empty-result behavior for private/invalid usernames, the one gap for a tool with a single required input.

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 coverage is 100% and the single parameter is documented in-schema as 'Instagram username (without @)'. The description adds no syntax, casing, or format detail beyond that, so the schema does the heavy lifting and baseline 3 applies.

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 and resource ('Fetch public profile information from Instagram') and enumerates exactly what comes back: bio, follower/following counts, post count, posts list, verification status, links. The Instagram-vs-TikTok distinction is unambiguous from the name plus the platform-specific return fields.

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?

Gives a concrete downstream chaining rule: each post id is a shortcode to pass to instagram_post for full post/reel/carousel details. It does not state exclusions, such as what happens for private, suspended, or nonexistent accounts, which leaves an edge case unaddressed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources