Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Media kit

instagram_media_kit
Read-onlyIdempotent

Build a partnership media kit with profile details, follower demographics, average reach, views, engagement by format across 30 and 90 days, and top posts; returns JSON and markdown.

Instructions

Partnership media kit: profile, follower demographics, average reach/views/engagement per format over 30 and 90 days, top posts. Returns JSON plus markdown. Demographic or insight failures only add warnings.

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_media_kit"
  }
}

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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's real contribution is the failure semantics: demographic or insight failures degrade to warnings instead of erroring, which tells the agent partial results are still returned. It also discloses the dual output format (JSON plus markdown). Pagination, size limits, and the cost/latency of a 90-day aggregation are not covered.

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?

Two tight sentences: first the contents, then the return format and degradation behavior. No filler, no restatement of the name, and the highest-value information is front-loaded. The compaction ("per format over 30 and 90 days") is dense but parseable.

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?

With no output schema, the description correctly takes on the job of describing the return payload (JSON plus markdown) and its sections, plus the partial-failure behavior. What is missing is scoping (which account is used by default) and any sense of response size for a 90-day aggregate.

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?

Schema description coverage is 100% and the single optional parameter already documents its alias semantics and default behavior, so the schema carries the load. The description adds nothing about the account parameter, which is acceptable at this coverage level but not additive.

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?

"Partnership media kit" plus an enumerated payload (profile, demographics, reach/views/engagement per format over 30 and 90 days, top posts) gives a specific resource and scope rather than a restatement of the title. It stops short of naming which sibling it replaces (e.g. instagram_performance_report or instagram_get_audience), so the differentiation is inferable rather than explicit.

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

Usage Guidelines3/5

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

The phrase "Partnership media kit" implies the sponsorship/pitch use case and the bundled 30/90-day window implies a reporting use case, but there is no explicit when-to-use or when-not-to-use instruction and no alternative tool is named. An agent must infer that this is the aggregate option versus the narrower insight tools.

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