Get Media Likes Users
get_likesGet instagram media likes users. Max - 12 Billing per call: 1 Credits.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| shortcode | No | Shortcode |
instagram-scraper
by com.jojapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description does not mention side effects, rate limits (the 'Billing' text is ambiguous), or what the returned data structure looks like. It is not clear if this is a read-only operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short, but includes confusing 'Max - 12 Billing per call: 1 Credits.' text that appears unrelated to the function and lacks clarity. It is not well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, and the description does not explain what the returned data contains (e.g., list of usernames, user objects). It lacks details on pagination, sorting, or any response format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description of 'shortcode' simply restates 'Shortcode' with no additional context about its format, purpose, or how it relates to the media. No added value over the schema.
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?
The verb 'Get' and resource 'instagram media likes users' clearly indicate the tool retrieves users who liked a specific media, distinguishing it from sibling tools like get_comments or get_followers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, nor any prerequisites or context. The description is a single line with no usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.4/5.0
Disambiguation2/5
Many tools have overlapping or near-identical purposes (e.g., get_posts vs get_posts_username, get_reels_posts vs get_reels_posts_username). The distinction between get_post_info, get_post_info_v2, get_reel, and get_tv_info is unclear from descriptions alone. This will cause frequent misselection.
Naming Consistency2/5
Naming is inconsistent: suffixes like '_username', '_hd', '_v2', '_id' appear sporadically, and the same resource type is named differently (e.g., 'posts' vs 'post_info' vs 'reels_posts' vs 'tv_posts'). Some tools are meta (get_requests, get_server) and deviate from the data-focused pattern. Overall, no clear naming convention.
Tool Count2/5
With 40 tools, the set is overly large for an Instagram scraper. Many tools are near-duplicates differing only by input type (ID vs username), which could be consolidated. The count far exceeds the typical 3-15 range and feels bloated, though not extreme.
Completeness4/5
The tool set covers a comprehensive range of Instagram data: user info, posts, reels, TV, stories, highlights, comments, likes, followers, followings, hashtag/location/music search, and even server status. Despite some vague tools (get_additional_info, get_basic_engagement), it appears functionally complete for the domain.