Download every slide of a public Instagram carousel post — photos and videos both. Returns an array of media URLs in the original slide order.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public Instagram carousel post URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that the tool works on public carousels only and returns media URLs in original order. No mention of error handling or rate limits, but the read-only nature is implied.
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 concise sentences: first states action and scope, second states output format. No redundant information, front-loaded and efficient.
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?
Simple tool with one parameter. The description covers purpose, input constraint (public), and output (array in order). Could mention error responses, but overall complete for expected use.
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% with a clear parameter description. The tool description adds that the URL must be a public carousel, but this is already in the schema. Minimal addition beyond schema, meeting baseline.
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?
Clearly states the tool downloads all slides of a public Instagram carousel post, including both photos and videos. Distinguishes from siblings like download_photo and download_video by specifying 'every slide' and 'carousel'.
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?
The description implies use for carousel posts, and sibling tool names (download_photo, download_video) provide context. However, it lacks an explicit when-to-use or when-not-to-use statement, though the purpose is clear enough.
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.