Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

instagram_user_highlights

Lists the Instagram story highlights a signed-out visitor can see for a profile handle, returning IDs, titles, cropped cover URLs, and owners for inspection or detail lookup.

Instructions

instagram: Story Highlights. GET /v1/instagram/user/highlights. List the story highlights a signed-out visitor sees on a profile: id, title, cropped cover URL and owner. Instagram shows signed-out visitors only some of an account's highlights. cover_media.thumbnail_src is always null; use cover_media_cropped_thumbnail.url. Pass the id to /v1/instagram/user/highlight/detail for the stories. Requires handle: a lookup by user_id needs a login and returns 400. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "instagram_user_highlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoThe Instagram username, with or without @ (required)
user_idNoNot supported: a lookup by user_id needs a login. Pass handle; user_id alone returns 400.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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 burden and does so: it discloses the signed-out visibility limitation (only some highlights are exposed), the always-null cover_media.thumbnail_src field and the correct substitute, and a precise cost model (1 credit on success; errors, blocked, timed-out, invalid and cache hits are free). This is unusually rich behavioral context for a read tool.

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?

Purpose is front-loaded in the first clause, followed by field list, the detail hand-off, the null-thumbnail caveat and the cost model. It is dense and a few fragments (the raw GET path) are redundant with the name, but every clause carries operational information.

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?

There is no output schema, so the description must describe the return shape, and it does (id, title, cropped cover URL, owner) while flagging the one trap field. Combined with the credit/error rules and the required-parameter constraint, an agent has everything needed to call it correctly.

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 coverage is 100% and the schema already documents handle as required and user_id as unsupported/400, so the description largely restates it. The extra value it adds is the 400-on-user_id outcome and the required-handle emphasis, but no syntax or formatting guidance beyond the schema example.

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 ("List the story highlights a signed-out visitor sees on a profile") plus the returned fields, and explicitly distinguishes itself from instagram_user_highlight_detail by naming that sibling as the next step. An agent can pick between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing: pass the returned id to /v1/instagram/user/highlight/detail for the stories. It also states the precondition (requires handle) and the negative case (a lookup by user_id needs a login and returns 400), leaving nothing to inference.

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