Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

instagram_user_posts

Retrieve the first 12 public Instagram grid posts for a handle, including reels, photos, videos, carousels, captions, URLs, images and dates; signed-out access is limited to 12.

Instructions

instagram: Posts. GET /v2/instagram/user/posts. Get the first 12 posts on a public profile's grid (reels, photos, videos and carousels): code, URL, media type, caption, display image and date, with the user. Only the first 12 are available signed out: next_max_id is always null and passing one returns 400; more_available says whether the profile has more. Like, comment and play counts are not in the signed-out grid; /v1/instagram/user/reels has counts for reels an 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": {
      "handle": "<handle>"
    },
    "name": "instagram_user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet to true for a trimmed response.
handleYesThe Instagram username, with or without @
next_max_idNoNot supported: signed-out pagination is closed, so only the first 12 posts are returned. Passing one returns 400.
require_play_countsNoAccepted for compatibility and ignored: the signed-out grid has no counts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses that next_max_id is always null and returns 400 if passed, that more_available signals whether the profile has more, that engagement counts are absent from the signed-out grid, and it spells out the credit/charging model including that errors and cache hits are free. This is well beyond what the schema conveys.

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?

Front-loaded with the core purpose and return fields, then the constraints, which is the right order. However, the final cost sentence is dense, and the sentence covering /v1/instagram/user/reels is truncated mid-word ('counts for reels an'), which slightly undermines polish.

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 no output schema, the description adequately names the key return fields (code, URL, media type, caption, display image, date, user, more_available) and the limits on results. A brief note on response shape or the meaning of 'trim' would close the remaining gap, but an agent can call this correctly as written.

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 parameters are already documented (including next_max_id returning 400 and require_play_counts being ignored). The description reinforces the pagination limitation but adds no new semantics for handle or trim; baseline 3 applies because the schema does the heavy lifting.

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 the first 12 posts on a public profile's grid') and enumerates the returned fields (code, URL, media type, caption, display image, date, user). The scope limit of 12 posts and the media types covered make it distinguishable from siblings like instagram_user_reels, which it explicitly notes carries play counts.

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?

Clearly signals the signed-out constraint and that pagination is unavailable, and points to /v1/instagram/user/reels when counts are needed. It does not explicitly route the agent away from instagram_profile or instagram_post for profile-level or single-post needs, so the when-not guidance is only partial.

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