Download an Instagram feed video (not a Reel) from a public post URL. Returns the original MP4 in whatever resolution the creator uploaded, no re-encoding.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public Instagram video post URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description bears full burden. It discloses output format (MP4, no re-encoding) but does not discuss rate limits, authentication, or whether the tool is read-only. Partial transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose and key details. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given one parameter and no output schema or annotations, description is fairly complete. Could mention potential errors (e.g., private videos) but adequate for a straightforward download tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but description adds meaning by specifying the URL must be a public Instagram video post (not a Reel), which goes beyond the schema definition.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it downloads an Instagram feed video (not a Reel) from a public post URL, specifying output format (original MP4, no re-encoding). Distinguishes from sibling tools like download_reels.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clear context for when to use (feed videos, not Reels), but lacks explicit exclusions or mention of alternatives. Sibling list provides indirect guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear distinct purposes; however, engagement_calculator and engagement_health_check have overlapping functionality, both dealing with engagement metrics, which could cause confusion.
Majority of tools follow a verb_noun pattern (e.g., download_photo, search_hashtags), but two tools start with nouns (engagement_calculator, engagement_health_check), breaking the consistency.
16 tools cover a wide range of Instagram-related tasks without being excessive. Each tool serves a specific purpose relevant to the toolkit's domain.
The toolkit covers downloading, engagement analysis, content generation, and hashtag research. Missing features like posting or advanced profile analytics are minor gaps for an analytical toolkit.