Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

instagram_user_embed

Retrieve the HTML embed widget for an Instagram profile by username to display profile content on a webpage. Private, missing, or non-embeddable profiles fail without using credits.

Instructions

instagram: Embed HTML. GET /v1/instagram/user/embed. Get the HTML of an Instagram profile's embed widget (instagram.com//embed/). Profiles that are private, missing or not embeddable fail at 0 credits. 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_embed"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe Instagram username, with or without @

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well by disclosing success and failure cost behavior, including private, missing, and non-embeddable profiles failing at 0 credits. It does not cover authentication or rate-limit behavior, and the phrase 'published cost' is somewhat circular, but the core billing and failure semantics are substantially transparent.

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?

The description is front-loaded with the endpoint and purpose, then follows with relevant cost behavior. It is mostly efficient, though the cost policy is somewhat repetitive and includes the vague 'published cost' reference.

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?

For a simple one-parameter GET operation, the description sufficiently explains the return value as embed HTML and covers the main failure and billing scenarios. With no output schema, it could say slightly more about the HTML response itself, but overall it is complete enough for correct invocation.

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%, and the schema already explains that the handle is an Instagram username with or without '@'. The description only reinforces this through the URL pattern instagram.com/<handle>/embed/, adding limited meaning beyond 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?

The description states a specific verb and resource: it returns the HTML of an Instagram profile's embed widget. By naming the embed widget and the URL pattern instagram.com/<handle>/embed/, it clearly distinguishes this tool from siblings that return profile data, posts, reels, or highlights.

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?

The description gives a clear context for when to use it: retrieving the HTML of an Instagram profile's embed widget. It does not explicitly name alternatives such as instagram_profile, but the narrow purpose makes the appropriate use case evident.

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