ig_get_publishing_limitCheck how many posts an Instagram account has published through the API in the last 24 hours and the daily publishing limit, so you can confirm remaining quota before posting.
How many posts the account has published through the API in the last 24 hours, and the limit (usually 100; carousels count as one).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real semantics beyond them: the window is a rolling 24 hours, the limit is usually 100, and carousels count as a single post. The one gap is that it doesn't say what happens when quota is exhausted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that front-loads the returned value and packs the counting rule into a parenthetical. Nothing is wasted and nothing essential is buried.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description carries the burden of describing the return, and it does so qualitatively (count plus limit). For a zero-parameter read tool with full annotation coverage, this is nearly complete; only the exhaustion/error behavior is unstated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is closed with additionalProperties=false and no fields, matching the description's account-level scope.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource (publishing quota) and metric (posts published via API in the last 24 hours) with the ceiling value. An agent can tell this apart from the posting siblings like ig_publish_post, though it never names an alternative to reinforce that.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied — the natural reading is 'call this before publishing to check remaining quota', but the description never says when to use it, when not to, or which sibling to pick instead. No prerequisites or rate-limit context for the call itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.