Skip to main content
Glama

instagram_post_image

Read-onlyIdempotent

Retrieves and displays a specific image from an Instagram carousel post using the original post's bootstrap data and Obscura's network, with slide selection.

Instructions

Show one carousel image using the exact post's bootstrap data and Obscura's network.

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_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
slideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. Beyond that, the description only adds an unexplained implementation detail ("Obscura's network") and does not say what is returned (image bytes, URL, or artifact), what happens for out-of-range slides, or how it interacts with prior post fetches. That leaves the behavioral burden essentially unmet.

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?

It is a single short sentence with the verb front-loaded, so it wastes no space. But its terseness is achieved by substituting opaque jargon for the information the agent actually needs, which is under-specification rather than true concision.

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

Completeness2/5

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

For a two-parameter tool with no output schema, the description should at minimum state what is returned (raw image vs. base64 vs. stored artifact) and how to address a specific slide. Neither is present, and the relationship to sibling tools that already capture or fetch post content is unexplained. It is not complete enough for confident invocation.

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?

Schema description coverage is 0%, so the description must explain the two parameters, and it does not. The required `url` parameter is never mentioned, and the `slide` parameter (default 1) — whose indexing base and valid range are critical for a carousel tool — is entirely absent from the description. The word "carousel image" implies slides exist but adds no usable semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Show one carousel image" gives a concrete verb and resource, so the agent knows roughly what happens. However, the qualifier "using the exact post's bootstrap data and Obscura's network" is internal jargon that does not clarify the outcome or distinguish this from neighbors like instagram_screenshot or instagram_snapshot. The purpose is only partially legible.

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 explicit when-to-use guidance and no named alternative tool for capturing post imagery. The phrase "the exact post's bootstrap data" hints at a prerequisite (post data must already exist), but nothing states when this tool is preferred over instagram_screenshot or how it differs. The agent must infer the routing decision.

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