Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Back up account

instagram_backup_account
Idempotent

Download an Instagram account's media incrementally to a local downloads folder, skip previously saved items, and write an insights-latest.json file for review.

Instructions

Incrementally download all of the account's media into the local downloads directory (skipping items already downloaded) and write insights-latest.json. max_items caps how many recent items are considered (default 500). Per-item failures do not abort the run.

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

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.
max_itemsNoMaximum media items to consider (default 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the local filesystem side effect (media files plus insights-latest.json), the incremental skip behavior, and partial-failure semantics ('per-item failures do not abort the run'). These are exactly the behavioral traits an agent needs for a long-running bulk write, though the location and contents of the JSON artifact remain unspecified.

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?

Three tight sentences, each carrying a distinct fact (what it does, how max_items scopes it, how failures are handled), with the core action front-loaded and no filler.

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 only two optional parameters, full annotation coverage, and no output schema, the definition covers what an agent needs to call it safely. Minor gaps remain around the exact destination directory and what insights-latest.json contains, but they do not block correct invocation.

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 parameters are already documented. The description adds only the nuance that max_items bounds how many *recent* items are considered, which clarifies selection order but is a small increment over the schema text.

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 and resource: incrementally download all of the account's media to the local downloads directory and write insights-latest.json. This differentiates it from instagram_download_media by emphasizing bulk, incremental backup and a JSON artifact, though no sibling is named 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 implied rather than stated: 'incrementally' and 'skipping items already downloaded' tell the agent this is a repeatable bulk operation, distinguishing it from single-item downloads. There is no explicit when-to-use/when-not guidance or named alternative such as instagram_download_media.

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