instagram-mcp

publishing_limit

Check your remaining Instagram posts allowed within the current 24-hour publishing quota to avoid hitting daily API limits.

Instructions

Remaining posts in the rolling 24h publishing quota (Instagram caps API posts/day).

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

Input Schema

Name	Required	Description	Default
`account`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jul 29, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context about the rolling 24h window and Instagram's cap, but does not explicitly state that the tool is read-only, whether authentication is required, or how the optional account parameter affects the result. The output schema likely covers the return shape.

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?

One concise, front-loaded sentence contains the core purpose and the key Instagram cap context. There is no filler or redundant information.

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

Completeness3/5

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

The description is adequate for a simple read-only tool with an output schema, but it leaves the account parameter completely unexplained and does not explicitly connect this to pre-publishing workflow. Minor gaps reduce its completeness.

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?

The only parameter, 'account', has zero schema description and is not mentioned in the tool description. The agent must infer that it selects which account's quota to check and what null means, which is a significant gap for a multi-account tool.

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 clearly identifies the tool as returning the remaining posts in the rolling 24h publishing quota, with the Instagram API cap context. It is specific enough to distinguish from publishing and media tools, though it does not explicitly name a sibling alternative.

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 quota context implies this should be checked before publishing to avoid hitting the cap, but the description does not explicitly say when to use it, when not to use it, or mention alternatives. Usage is inferred rather than stated.

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