show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Show' is consistent with them. The description adds the object scope (platform and adapter versions) but no further behavioral context, which is acceptable given the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that states exactly what the tool returns. It is front-loaded and contains no filler.
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?
For a zero-parameter, read-only version query, the description is complete enough for an agent to select and invoke the tool correctly. No output schema exists, but the stated result concept is sufficient.
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 tool has zero parameters, so there is no parameter semantics for the description to clarify. The baseline of 4 applies because nothing is missing.
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 description states a specific verb and resource: 'Show the current MCP platform and adapter versions.' It is clear and specific, but it does not explicitly differentiate itself from sibling tools such as toolkit_info, so it misses the top score.
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?
There is no guidance about when to use this tool versus alternatives or when not to use it. The sentence only describes what the tool does, leaving usage context entirely implied.
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
B3.4/5.0
Disambiguation3/5
Several tools pair up with near-identical purposes (instagram_actions_list_comments vs instagram_get_ig_media_comments, instagram_create_carousel_container vs instagram_post_ig_user_media, instagram_actions_send_message vs instagram_send_text_message), so an agent can easily select the wrong one. The detailed descriptions clarify the differences, but the overlapping unofficial-actions and official-API surfaces still create ambiguity.
Naming Consistency3/5
Most Instagram tools follow snake_case verb_noun naming with an instagram_ prefix, but the prefix is applied inconsistently (generic tools like authenticate, connect, and marketplace lack it) and verbs vary among actions_*, get_*, list_all_*, post_*, send_*, and create_*. The names are readable but do not form one predictable pattern.
Tool Count2/5
33 tools is well above the 25-tool threshold, and the set includes several non-Instagram platform tools (marketplace, report_bug, show_version, toolkit_info) that belong to the MCP platform rather than an Instagram domain. The Instagram-specific surface is broad enough that splitting or trimming would improve coherence.
Completeness3/5
The server covers a broad range of Instagram workflows: auth, follow/unfollow, likes, comments, stories, messaging, media publishing, and insights. However, obvious lifecycle counterparts are missing—no unlike, no delete/update media, and no delete/unlike comments—so the surface has notable gaps.