Skip to main content
Glama

captapi

by io.github.CDCStream

instagram_highlights

Persistent Story Highlight albums for a public profile — id, title, cover, owner. Flat 1 credit. Costs 1 credit. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoInstagram profile URL, @handle, or username. Omit when userId is set.
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
userIdNoNumeric Instagram user ID. Prefer when known — skips handle→ID resolve. When only userId is set we reverse-resolve the username so the WPI / profile-HTML shelf can still run.

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and covers pricing (flat 1 credit), cache behavior (cache=true free 24h hit, default fresh), and the guarantee that empty results/failures aren't charged. It doesn't discuss rate limits or auth, but for a simple public read tool the key operational behavior is disclosed.

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 short and front-loads the core purpose before pricing/caching details. The only blemish is redundancy—'Flat 1 credit. Costs 1 credit.'—which keeps it from top marks.

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 low-complexity tool with fully documented schema, the description covers what the tool returns, cost, cache, and failure charging. It could be more complete by explicitly noting the relationship to instagram_highlights_details, but nothing essential is missing for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all three parameters at 100% coverage. The description adds value beyond the schema by explaining the cache parameter's effect and the default freshness behavior, which is directly actionable for invocation.

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

Purpose4/5

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

States the resource and returned fields (id, title, cover, owner) clearly, and 'for a public profile' sets scope. However it lacks an explicit verb and does not directly distinguish itself from the sibling instagram_highlights_details, so it falls short of a 5.

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

Usage Guidelines3/5

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

The description implies this is for retrieving a profile's highlight albums and gives clear context (public profile, cache behavior), but it never states when to choose this tool over the similar instagram_highlights_details or other Instagram tools. No exclusions or alternatives are mentioned.

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

All captapi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation3/5

The platform-prefix convention keeps most of the 178 tools clearly separated, but several clusters are genuinely ambiguous: tiktok_live_info is explicitly described as 'Identical to TikTok Live', instagram_basic_profile and instagram_channel_details both return profile stats, and facebook_profile_posts overlaps with facebook_profile_reels. The generic 'Summarizer' descriptions for facebook_summarize, instagram_summarize, and tiktok_summarize provide no disambiguating detail at all.

Naming Consistency4/5

The dominant snake_case platform_resource_suffix pattern is followed remarkably consistently across 178 tools (e.g. youtube_channel_videos, tiktok_search_users, reddit_subreddit_posts). Minor deviations exist: the same creator resource is called 'channel' in some tools (tiktok_channel_details, instagram_channel_posts) but 'profile' or 'user' in others (facebook_profile_posts, twitch_user_videos, linnkme_profile); link-in-bio tools mostly use _page but linkme uses _profile; and the video_summarize/video_transcript pair lacks a platform prefix.

Tool Count2/5

At 178 tools this is far beyond what any agent can efficiently navigate in a single flat namespace, and even individual platform subsets exceed reasonable bounds (TikTok alone has ~34 tools, YouTube ~25). The sheer breadth of the multi-platform scope partially justifies the count, but the server would be far more usable split into per-platform servers.

Completeness4/5

The read-only data surface is impressively thorough: nearly every platform has profile + content + search + comments coverage, and TikTok, YouTube, Instagram, and Facebook are covered end-to-end including shops, ads, transcripts, and summaries. Notable gaps are minor: Twitter has no keyword search tool, LinkedIn lacks comments, and Reddit has no user-profile endpoint, but none of these create dead ends for the server's core data-retrieval purpose.

Resources