Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Snapshot insights

instagram_snapshot_insights

Captures current Instagram follower counts and last-24-hour account insights into a local snapshot, feeding growth reports for read-only analysis.

Instructions

Fetch current counts and last-24h account insights and store them as a local snapshot (the daemon also does this daily). Feeds instagram_get_growth. Allowed under read_only.

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": "instagram_snapshot_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and non-destructive; the description adds the crucial detail that the write is a local snapshot rather than a remote mutation, that a daemon replicates it daily, and that it is 'Allowed under read_only'. That resolves what would otherwise be a puzzling readOnlyHint=false on an insights tool.

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?

Three short sentences, front-loaded with the action and its side effect, then the downstream consumer, then the policy note. Every sentence carries distinct information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter tool with no output schema and a local-mutation side effect, the description covers what is fetched, what is stored, who else triggers it, and which tool consumes it. Minor gaps: where the snapshot lives and whether repeated calls overwrite it, which is relevant given idempotentHint=false.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 100% schema description coverage ('Account alias; defaults to the configured default account'), so the schema already carries the semantics. The description adds nothing about the account parameter itself, which matches the baseline 3 for fully documented schemas.

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?

Names a specific verb and resource ('Fetch current counts and last-24h account insights') plus a concrete side effect ('store them as a local snapshot'), which distinguishes it from the pure-read insight siblings. It does not explicitly contrast itself with instagram_get_account_insights, so differentiation is partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real usage context: the result 'Feeds instagram_get_growth', a daemon already runs it daily (implying manual calls are often redundant), and it is permitted under read_only mode. No explicit when-not or named alternative for the insight-fetching case, keeping it below a 5.

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

Deploy Server

Other Tools