Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

post_get

Read-only

Fetches Instagram post or reel details from a URL, including author, timestamp, media type, caption, and visible like and comment counts.

Instructions

Detail sebuah post/reel: penulis, waktu, jenis media, dan teks halaman (caption, jumlah like/komen bila tampil).

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": "post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral detail beyond that — the field set returned and the qualifier 'bila tampil' (when displayed), signalling that counts are conditional and may be absent. It says nothing about private/deleted posts, invalid URLs, or auth requirements, so it stops short of full disclosure.

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?

One compact sentence that front-loads the resource and then lists return fields with no filler. Slightly telegraphic, but every clause carries information.

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 read-only single-resource getter with one parameter and no output schema, the description adequately covers what comes back. It leaves the URL format contract and failure modes (private account, nonexistent post) unaddressed, which an agent would need before calling confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'url' has 0% schema description coverage and the description never mentions it. It does not say whether a full permalink, shortcode, or reel URL is expected — exactly the kind of meaning the description should supply when the schema is bare.

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 the specific resource (a post/reel) and enumerates what it returns: author, time, media type, caption, and like/comment counts. That is enough to separate it from siblings such as post_comments or post_like, though the verb is implicit ('Detail ...') rather than an explicit 'retrieve'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of alternatives (e.g. explore_posts, user_posts, feed_home), and no prerequisites. The agent must infer from the name alone that this fetches a single post by URL.

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