Skip to main content
Glama

Download media

instagram_download_media
Idempotent

Download an Instagram media item to your local downloads folder with a JSON sidecar, including carousel children and video thumbnails; existing files are skipped and no credentials are sent.

Instructions

Save one of your media items (and carousel children, video thumbnails) to the local downloads directory with a JSON sidecar. Only Instagram CDN hosts are fetched, no credentials are sent, and existing files are skipped. Writes local files only.

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": {
      "media_id": "<media_id>"
    },
    "name": "instagram_download_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.
media_idYesInstagram media id.
include_childrenNoDownload carousel children (default true).
include_thumbnailNoDownload video thumbnails (default true).

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?

The annotations already declare the safety profile: not read-only, open-world, idempotent, not destructive. The description explains the mechanisms behind those hints in ways the annotations cannot: only Instagram CDN hosts are fetched, no credentials are forwarded, existing files are skipped, and writing is restricted to local files. What it omits is where the downloads directory is and what the JSON sidecar contains, both of which matter for a tool that writes files.

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, with zero preamble: the first states the action and what is downloaded, and the second gives the safety guarantees. The scoping statement at the end reinforces rather than repeats the opening, and no sentence could be removed without losing information.

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?

There is no output schema, so the description should cover what comes back. It partially does by mentioning a JSON sidecar and by describing file-skipping behavior. What it does not give is the returned path or reference, which would fully close the loop for an agent that needs to locate the saved file.

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 100%, so every parameter is already documented, including the documented defaults for include_children and include_thumbnail. The description only echoes the carousel-children and video-thumbnail concepts without adding format, size limits, or media_id constraints. The baseline score of 3 is therefore the right score, with the schema carrying most of the load.

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?

The description opens with a specific verb and resource: save a media item to the local downloads directory, with carousel children and video thumbnails included. It also closes with a scoping line, "Writes local files only," which separates it from the read-only metadata siblings. It never names instagram_get_media or instagram_backup_account explicitly, so the agent must infer that this tool writes to disk while those do not.

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 phrase "Save one of your media items" implies when to use the tool, and "existing files are skipped" implies that re-running it is safe. However, the description never states when to prefer this over instagram_get_media for metadata or instagram_backup_account for bulk copies, and gives no exclusion. An agent can infer the cases where this is the right tool, but only loosely.

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