Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

media_urls

Read-only

Extract image and video file URLs from an Instagram post for downloading or processing by an AI agent.

Instructions

Ambil URL file gambar/video dari sebuah post (untuk diunduh/diolah agent).

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": {
      "url": "<url>"
    },
    "name": "media_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network scope are covered. The description adds a useful behavioral hint that the result is URLs intended for download rather than the media bytes themselves. It does not disclose what happens for text-only posts, carousel ordering, or link expiry.

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?

One short sentence, front-loaded with the action and resource, with the use case appended in parentheses. Nothing is wasted or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with annotations and no output schema, the definition is close to sufficient but leaves the return shape unexplained — whether it yields one URL or a list for multi-media posts is not stated. Adding that would remove the last ambiguity for an agent.

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 0% for the single 'url' parameter, so the description must carry meaning — and 'dari sebuah post' does imply the parameter is a post reference. However, it never specifies the accepted format (post shortcode, permalink, or media URL), leaving the agent to guess.

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 names a specific verb and resource: 'Ambil URL file gambar/video dari sebuah post' — retrieve image/video file URLs from a post. That is clearly distinct from generic siblings like post_get or feed_home. It does not explicitly name a sibling it supersedes, so a 5 is not warranted.

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 parenthetical '(untuk diunduh/diolah agent)' signals the intended downstream use — feeding download or processing pipelines — which implies when to reach for it. There is no explicit guidance on when NOT to use it versus post_get, nor any prerequisite such as whether the post must be public.

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