Skip to main content
Glama
Sign In

Bridgly

by app.bridgly.mcp
OverviewDiscussionsAdmin

Instagram: List profile highlights

instagram_highlights
Read-onlyIdempotent

List saved story highlights on a public Instagram profile, including highlight IDs, titles and cover images. Use a highlight ID with the highlight endpoint to retrieve its stories. Continue with nextCursor. Read-only: returns public data and changes nothing. Costs 1 credit per request.

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

Input Schema

NameRequiredDescriptionDefault
countYesNumber of results to return (1–10). Defaults to 10.
cursorNoThe previous response's `nextCursor`, to fetch the next page. Omit it for the first page.
usernameYesInstagram username, or the profile link, e.g. "instagram" or "https://www.instagram.com/instagram/".
cacheOnlyNoReturn only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.
cacheMaxAgeHoursNoAccept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cacheMaxAgeHours
      Added value: +{
+  "description": "Accept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / cacheOnly
      Added value: +{
+  "description": "Return only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / username / description
      Previous value: -"Instagram username, or the profile link, e.g. \"instagram\" or \"https://www.instagram.com/instagram/\""New value: +"Instagram username, or the profile link, e.g. \"instagram\" or \"https://www.instagram.com/instagram/\"."
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, and the 'Read-only: returns public data and changes nothing' sentence largely restates them. However, 'Costs 1 credit per request' is behavioral context the annotations do not carry, and the mention of pagination via nextCursor adds operational guidance beyond structured data.

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?

Four short sentences, front-loaded with the resource and payload, then usage, pagination and cost. Only the read-only sentence is near-redundant with the annotations, a minor inefficiency rather than clutter.

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?

With no output schema, the description compensates by naming the returned fields, and it covers the follow-up workflow, pagination and per-request cost. An agent has everything needed to call it correctly and to act on the result.

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 username, count, cursor, cacheOnly and cacheMaxAgeHours are already fully documented, and the description adds no new detail on their formats or limits. Mentioning nextCursor continuation only echoes the cursor parameter's schema text, so the baseline 3 applies.

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 saved story highlights on a public Instagram profile) and enumerates the returned payload (highlight IDs, titles, cover images). This distinguishes it clearly from the singular instagram_highlight sibling, which retrieves the stories inside one highlight.

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?

Explicitly routes the agent forward: pass a returned highlight ID to the highlight endpoint to get stories, and use nextCursor to paginate. It does not state when this tool should be avoided (e.g. private profiles or when only a single highlight is wanted), which keeps it short of a 5.

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

All Bridgly toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources