Skip to main content
Glama

Instagram profile and posts

instagram_profile
Read-only

Instagram Profile & Posts: one public Instagram account by handle or URL: name, bio, followers, following, post count, verification, then its recent posts and reels with caption, likes, comments, views, image link and time, in the shared social schema; next_cursor pages through the full post feed. Bad input is free; not found or no match is not charged. Price: $0.02 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "handle": "<handle>"
    },
    "name": "instagram_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNonext_cursor of the previous page.
handleYesAn Instagram handle (with or without @) or an instagram.com profile URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing commercial behavior: $0.02 per successful call, x402/USDC-on-Base payment passed in _meta['x402/payment'], and the billing carve-outs (bad input free, not-found not charged). Annotations already cover read-only/open-world semantics, so this pricing and failure-charging detail is the real added value; only the return-shape caveats (e.g. what happens when the account exists but has zero posts) are left implicit.

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?

Front-loaded with the resource and payload, then pagination, then billing — a sensible order with no filler. The semicolon-chained clauses make it denser than it needs to be, but every clause carries information an agent needs.

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 return-value burden and does so by listing profile fields and per-post fields plus the shared schema and cursor pagination. Pricing and error-charging rules round it out. Minor gap: nothing about rate limits, result caps per page, or behavior on private accounts.

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%, so both handle (with/without @ or full URL) and cursor are already documented in the schema. The description adds only the useful nuance that next_cursor pages through the full post feed, which is a marginal gain over the schema's own wording. 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 resource (one public Instagram account, by handle or URL) and enumerates exactly what is returned: profile fields plus recent posts and reels with their metrics, in a shared social schema. The platform name plus 'one account' framing separates it cleanly from the multi-platform siblings such as x_profile, tiktok_followers, or social_search.

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?

Implies the usage condition ('one public Instagram account by handle or URL') and the pagination path via next_cursor, but never states when to prefer a sibling tool or what to do when the account is a private/non-public one. An agent can infer the context but is given no explicit exclusions or alternatives.

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.