instagram-mcp

Publishing quota

ig_publishing_limit

Read-onlyIdempotent

Check how many posts an account has published via the Instagram API in the last 24 hours to stay within the 100-post limit, counting each carousel as one.

Instructions

How many posts the account has published via the API in the last 24 hours (limit: 100; a carousel counts as one).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 18, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful domain semantics the annotations cannot express: the rolling 24-hour window, the numeric cap, and the carousel accounting rule. It stops short of saying what happens at the limit or whether the count is account-wide or app-wide.

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 sentence that front-loads the measurement, then qualifies it with the two rules that matter (limit and carousel counting). 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 no-parameter read with no output schema, the description supplies enough to interpret the result: it is a count, scoped to the last 24 hours, against a limit of 100. It could note the response shape (a number vs. an object with limit/remaining), but the gap is minor.

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?

The tool takes zero parameters, so the schema has nothing to document and the baseline of 4 applies. The description correctly adds no parameter noise.

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 measurement: the count of posts published via the API in the last 24 hours, including the 100-post cap and the carousel-counts-as-one rule. This is clearly a quota-read tool, easily distinguished from the ig_publish_* siblings that consume that quota.

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?

Usage is only implied: mentioning the 100-post limit and 24-hour window suggests checking before publishing, but the description never says when to call it, whether it is a pre-publish check, or what to do if the limit is reached. No alternative tool is named.

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