Skip to main content
Glama
mathieubernardi

meta-mcp-py

get_ig_media

Retrieve detailed information about a specific Instagram post by providing its media ID. Get captions, media type, and engagement metrics from Meta's Graph API.

Instructions

Détaille une publication Instagram.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
media_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says the tool 'details' a publication and does not mention read-only status, required Instagram access token scopes, or any constraints on the media object. This is a significant gap for a tool that likely requires page/Instagram account authorization.

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 a single, front-loaded sentence with no filler, which is concise. However, it is so terse that it omits useful context; the brevity is acceptable but not exemplary for a tool with a non-obvious parameter format.

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?

The tool is simple and has an output schema, but the description does not situate it among many IG-related siblings or explain prerequisites. Missing context includes how to obtain media_id, what scopes are required, and what kind of media is covered (image, video, carousel, reel).

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?

Schema description coverage is 0% and the description adds no meaning about media_id beyond its property name. No format, example, or source guidance is given, so an agent may guess whether the ID is a numeric IG media ID, a shortcode, or something else.

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 French description uses a clear verb ('Détaille') and a clear resource ('une publication Instagram'), indicating that the tool retrieves details for a single Instagram media object. It is distinguishable from siblings like list_ig_media by implying singular detail retrieval, though it does not explicitly contrast with get_ig_media_insights.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives such as list_ig_media or get_ig_media_insights, so an agent must infer selection solely from the tool name.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mathieubernardi/Meta_Business_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server