insta-pilot

ig_analytics

Read-only

Analyze Instagram account performance by identifying high- and low-performing posts, ideal posting days and hours, and average engagement and views.

Instructions

Análisis de rendimiento: top/peores publicaciones, mejores días y horas para publicar, medias de engagement y views.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ig_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`posts`	No
`account`	No	Usuario de Instagram configurado (por defecto la cuenta activa)
`time_zone`	No		Europe/Madrid

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read profile is covered. The description adds the scope of analysis (aggregate engagement/views stats over posts), but says nothing about defaults, lookback windows, rate limits, or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that lists the metrics efficiently with no filler. It is underspecified rather than bloated, but the structure itself is tight.

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?

No output schema exists, and the description does not describe the shape of the returned analytics (groupings, time granularity, units). Combined with two undocumented parameters, an agent lacks enough to call it confidently or anticipate the result.

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 only 33% (only the 'account' param is documented). The description mentions no parameters at all, so it does not compensate for the undocumented 'posts' and 'time_zone' fields or clarify their effect on the analysis.

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 names the resource ('Análisis de rendimiento') and enumerates the concrete outputs (top/worst posts, best days/hours, engagement and views averages), so an agent can tell what it produces. It stops short of differentiating itself from analytics siblings such as ig_media_insights and ig_account_insights, which also report performance metrics.

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 statement of when to use this tool versus the many analytics/insights siblings (ig_media_insights, ig_account_insights). The agent must infer the distinction from the metric list alone.

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