Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

instagram_post

Fetch public Instagram post or reel data by URL as a signed-out visitor, including media links, caption, owner, engagement counts, date, location, and optional reel play count.

Instructions

instagram: Post/Reel Info. GET /v1/instagram/post. Get a public Instagram post or reel by URL (/p/, /reel/, /reels/ or /tv/), as a signed-out visitor sees it: media URLs, caption, owner (with follower count), like and comment counts, duration, music, date and location. video_view_count is Instagram's older view count; for the plays Instagram shows on a reel, set include_play_count=true. Comment edges are empty (comments need a login). Private or removed posts fail at Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the post or reel
trimNoSet to true for a trimmed response.
regionNoAccepted for compatibility. Instagram's public pages are read from the US.
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.
download_mediaNoNot supported: download_media=true returns 400. Use video_url or display_url in the response.
include_play_countNoSet to true to add play_count (also as video_play_count) for a reel: the plays Instagram shows, the same number as /v1/instagram/user/reels. Read from the owner's 12 newest reels; null for older ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it discloses the signed-out visibility model, that comments are unavailable without login, that private/removed posts fail, and that download_media=true returns 400. It also describes the credit model in detail, including that errors, blocked or timed-out requests, invalid requests and cache hits cost nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded with the core verb and route first, which is good. However, the pricing paragraph is dense and contains a garbled fragment ('Private or removed posts fail at Costs 1 credit when it succeeds'), which undercuts readability on an otherwise well-organized block.

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

Completeness5/5

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

For a six-parameter read tool with no output schema, the description covers what is returned (media URLs, caption, owner with follower count, like/comment counts, duration, music, date, location) and qualifies the edge cases agents will hit. Nothing essential for correct invocation appears to be missing.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3, but the description adds useful meaning: it distinguishes video_view_count (Instagram's older count) from the plays returned via include_play_count, and reiterates the download_media prohibition with the recommended substitute fields. This helps an agent choose parameter values rather than merely restating the schema.

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 verb and resource ('Get a public Instagram post or reel by URL') plus the route (GET /v1/instagram/post) and the accepted URL forms (/p/, /reel/, /reels/, /tv/). An agent can tell this apart from listing tools like instagram_user_posts without opening the schema.

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

Usage Guidelines4/5

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

Gives clear context for when to use it (single public post/reel by URL, signed-out view) and several when-not conditions: comment edges are empty, private or removed posts fail, and download_media is unsupported. It does not explicitly route to a sibling for listing or login-only data, so it falls short of the full when/when-not/alternative standard.

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