Skip to main content
Glama

get_publishing_limit

Read-onlyIdempotent

How much of Instagram's publishing allowance the account has used in the current rolling window (about 24 hours), straight from Instagram.

Check it before scheduling a big batch (schedule_reels_bulk, several posts for one day) so the user hears about a limit now rather than from a failed post later. used counts posts already PUBLISHED through the API in the window — posts still waiting in the queue are not counted yet, so subtract the ones list_scheduled_posts shows going out in the same window from remaining before promising capacity.

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": {
      "workspace_id": "<workspace_id>",
      "ig_account_id": "<ig_account_id>"
    },
    "name": "get_publishing_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes
ig_account_idYes

Output Schema

NameRequiredDescriptionDefault
noteYes
usedYes
totalNo
remainingNo
window_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare this a safe, idempotent, non-destructive read, so the description is free to spend its words on semantics the annotations cannot express. It discloses the window definition (rolling, ~24 hours), the critical caveat that `used` counts only posts already PUBLISHED via the API and excludes queued posts, and the implication that `remaining` therefore overstates true capacity. That is exactly the kind of subtle behavior an agent would otherwise get wrong.

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?

The first line front-loads the resource and its meaning; the second gives the decision rule; the third sharpens the return-value semantics. Three sentences, each doing distinct work, with no restated name/title boilerplate.

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?

An output schema exists, so the description needn't enumerate return fields, yet it still explains the two fields that are easy to misread (`used` vs `remaining`) and the queue exclusion. For a two-argument read-only lookup, nothing an agent needs in order to call it or interpret it correctly is missing.

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?

Schema description coverage is 0%: workspace_id and ig_account_id are bare string types with no documented meaning, format, or sourcing. The description never mentions either parameter, so it does not compensate for the gap, though the names are largely self-explanatory identifiers, which keeps this from being a 1.

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 resource (Instagram publishing allowance) and precisely what is returned (how much of the rolling ~24h window is used), plus that the value is authoritative ('straight from Instagram'). That scope is distinguishable from siblings like get_plan_usage or list_scheduled_posts without opening any schema.

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

Usage Guidelines5/5

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

Explicitly tells the agent when to call it ('before scheduling a big batch') and names the concrete trigger tools (schedule_reels_bulk, several posts for one day). It also routes the agent to a complementary tool (list_scheduled_posts) for a specific follow-up calculation, which is real usage guidance rather than generic advice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources