Skip to main content
Glama
Upload-Post

Upload-Post

Official

Get publishing limits

get_publishing_limits
Read-only

Check how many Instagram or Threads posts a connected profile can still publish in the current rolling 24-hour window, and refresh the cached limit on demand.

Instructions

How many posts Instagram or Threads still lets the connected account publish: both networks cap posts per rolling 24 hours, and a post over the cap fails. Cached; refresh: true reads it again from the network.

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": {
      "platform": "<platform>",
      "profile": "<profile>"
    },
    "name": "get_publishing_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesUpload-Post profile name with that network connected.
refreshNoSkip the cache.
platformYes

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld/non-destructive, and the description adds real value on top: results are cached, `refresh: true` re-reads from the network, and the cap is a rolling 24-hour window whose breach causes publish failure. It stops short of noting rate limits or cache staleness windows.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the core question, with the cache behavior trailing as supporting detail. The phrasing 'How many posts Instagram or Threads still lets the connected account publish' is slightly tangled but wastes no words.

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?

An output schema exists, so return-value shape need not be described. For a three-parameter read tool with annotations, the description covers cap semantics, cache behavior, and the consequence of exceeding the limit — enough for correct invocation, missing only explicit sibling routing.

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 67%, and the description compensates on the weakest parameter by explaining exactly what `refresh: true` does (bypasses cache, re-queries the network) rather than just restating 'Skip the cache.' It also ties `profile` to 'the connected account,' though it adds no detail on the platform enum beyond what the schema's enum already conveys.

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?

States a specific quantity (remaining posts) for a specific resource (Instagram/Threads publishing caps) with the mechanism spelled out as a rolling 24-hour window. It does not reference the sibling tiktok_publishing_settings, so an agent must infer on its own that TikTok limits live elsewhere.

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 note that 'a post over the cap fails' implies the check should precede publishing, but the description never states that condition explicitly or names alternatives. Usage context is inferable rather than prescribed.

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