Skip to main content
Glama
Sign In
Instagram MCP

Instagram MCP

by nelsonrogers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Raw Instagram API query

query_instagram_api
Read-onlyIdempotent

Run read-only GET requests against Instagram Graph API paths to retrieve raw JSON for account insights, media, comments, or other endpoints when no specialized tool fits.

Instructions

Run any read-only GET on Meta's Instagram Graph API for the connected account and return Meta's raw JSON: the escape hatch when no other tool fits. Account insights allow at most 30 days between since and until (Unix seconds) and go back 2 years. Pagination: pass 'after' from paging.cursors. Meta's error message is returned if a request is invalid.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "query_instagram_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesGraph API path, relative: 'me' is the connected account, e.g. 'me/insights', 'me/media', '<media-id>/insights', '<media-id>/children'.
paramsNoQuery parameters, e.g. {'metric': 'views,reach', 'period': 'day', 'metric_type': 'total_value', 'since': '1730000000', 'until': '1732000000'}.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly/openWorld/idempotent/non-destructive), the description discloses operational constraints the agent cannot infer: the 30-day max window between since/until for account insights, a 2-year lookback limit, the pagination protocol via paging.cursors 'after', and that Meta's own error text is surfaced on invalid requests.

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?

Four tight sentences, each carrying distinct information: identity/fallback role first, then limits, then pagination, then error behavior. No filler or restated field names.

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

Completeness5/5

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

For a raw pass-through API tool with an output schema already defined, the description covers the remaining risks an agent needs — scope of paths, date-window caps, pagination, and error surfacing — leaving nothing material unstated before invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds meaning by specifying that since/until are Unix seconds with a 30-day cap and by identifying the 'after' value from paging.cursors as the pagination parameter, which the schema only gesture at via an example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Run any read-only GET on Meta's Instagram Graph API') plus the return format ('Meta's raw JSON'), and explicitly positions itself as 'the escape hatch when no other tool fits', which separates it from the specific get_instagram_*/list_instagram_* siblings.

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?

Provides a clear selection rule: use this only when no other tool fits, which tells the agent to prefer the purpose-built siblings. It does not name which specific alternative covers which need, but the fallback framing is unambiguous enough to route correctly.

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