meta_organic_get_ig_mediaRecent Instagram media with engagement and insights.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| days | No | ||
| limit | No | ||
| date_to | No | ||
| page_id | No | ||
| sort_by | No | ||
| user_id | No | ||
| site_url | No | ||
| client_id | No | ||
| date_from | No | ||
| ad_account | No | ||
| ig_user_id | No | ||
| user_email | No | ||
| range_preset | No | ||
| activity_only | No | ||
| campaign_name | No | ||
| property_name | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that - no note on pagination, what 'insights' requires, or how the 17 optional filters interact - and the output schema only covers return format.
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?
It is a single front-loaded sentence with no filler, which is structurally clean. However, at this level of terseness for a 17-parameter tool it reads as under-specification rather than disciplined concision.
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?
For a tool with 17 optional parameters, zero schema descriptions, and no annotations carrying behavioral detail, the description does not supply nearly enough for correct invocation. An output schema covers return values, but selection and filtering semantics are entirely unaddressed.
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 description coverage is 0% across 17 parameters, and the description mentions none of them by name or meaning. 'Recent' faintly implies a time window, but the distinction between days, date_from/date_to, range_preset, and sort_by is left completely undocumented.
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?
The phrase 'Recent Instagram media with engagement and insights' names the resource (Instagram media) and hints at returned fields, but offers no verb and no differentiation from close siblings like meta_organic_get_ig_insights or meta_organic_get_page_posts. An agent cannot tell from this sentence alone which organic Instagram tool to pick.
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?
There is no when-to-use guidance, no mention of prerequisites (connected IG account, page/IG user id), and no routing to the many sibling tools. The agent is left to infer applicability from the tool name entirely.
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.