Skip to main content
Glama
Sign In

Instagram Data

by io.github.FastSocialCo
OverviewDiscussionsAdmin

Get Instagram story highlights

instagram_highlights
Read-only

Get Instagram story highlights. Title, cover image and item count for each highlight. Pass an id to /v1/highlight for its items.

Cost: 3 credits.

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": {
      "username": "<username>"
    },
    "name": "instagram_highlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesInstagram handle, with or without @. A profile URL also works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / user_id
      Removed value: -{
-  "description": "Numeric Instagram user id. Pass this or username.",
-  "type": "string"
-}
    • changedInput schema / properties / username / description
      Previous value: -"Instagram handle, with or without @. A profile URL also works. Pass this or user_id."New value: +"Instagram handle, with or without @. A profile URL also works."
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "username"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful context beyond them: the exact return shape (title, cover image, item count), the fact that items require a follow-up call, and a concrete cost of 3 credits.

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

Conciseness5/5

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

Three short sentences with zero filler: purpose, return shape, and cost/routing all front-loaded. Every sentence earns its place and nothing is repeated from structured fields.

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 correctly compensates by naming the returned fields and explaining that item-level data lives behind another endpoint. Cost is disclosed as well; only pagination or rate-limit behavior is left unstated, a minor gap for a single-argument read tool.

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?

There is one parameter and schema coverage is 100%, so the schema fully documents username including @ handling and URL acceptance. The description adds nothing about this parameter (the 'pass an id' line concerns a different endpoint), which is the expected baseline when the schema carries the load.

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 Instagram story highlights') and enumerates what is returned (title, cover image, item count), so the agent knows exactly what this call produces. It also explicitly separates itself from the singular sibling instagram_highlight by noting that an id must be passed to /v1/highlight for the items.

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?

Provides explicit routing: use this tool for the highlight list, then pass an id to /v1/highlight for items — a clear alternative path that disambiguates the plural/singular sibling pair. It stops short of contrasting against instagram_stories or stating any preconditions, which keeps it out of the 5 range.

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

All Instagram Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources