Skip to main content
Glama
Hermoso

Hermoso

Official

See or resume a held Instagram account

instagram_posting_hold
DestructiveIdempotent

Check and lift a hold on an Instagram account’s scheduled posts when Meta’s spam restriction blocks posting; view queued count or resume and release waiting posts.

Instructions

See or lift the HOLD on an Instagram account's scheduled posts. When Meta refuses two posts in a row from an Instagram account with its spam restriction (code 4/2207051, "We restrict certain activity to protect our community"), Hermoso holds that account's scheduled Instagram posts instead of sending them into the restriction: they stay queued and nothing is posted. action:"status" (default) says whether posting is held, since when, and how many posts wait. action:"resume" lifts the hold and releases the waiting posts (ones whose time passed go out 30 minutes apart). Resume only after the user says the account holder has checked Account Status in the Instagram app. Reconnecting Instagram or a successful Instagram post also lifts it. Free.

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

Input Schema

NameRequiredDescriptionDefault
brandNoWHICH PROFILE — id or exact name from list_brands; needed when it is not the profile this connection is pinned to.
actionNostatus (default) or resume
accountNoresume one held account: its Instagram id or @handle (default: every held account on this brand)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.571

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive/openWorld/idempotent behavior, and the description adds substantial context on top: while held nothing is posted, resume releases waiting posts 30 minutes apart, and the tool is free. It does not cover edge cases such as calling resume on an account that is not held, or what the status output looks like structurally.

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?

The purpose is front-loaded in the first sentence, followed by the trigger condition, the mutation semantics, and the precondition for resume. It is dense but every sentence carries information; a few clauses are run-on and could be split for readability.

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?

For a three-parameter tool with no output schema, the description supplies the trigger condition, the effect of each action, the release timing, the precondition, and the cost. An agent has enough to call it correctly and to explain the consequences to a user before resuming.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so brand, action, and account are already documented, including the default-to-all-held-accounts behavior for account. The description reinforces the default for action:status and the effect of resume but adds little syntax or format detail beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb and resource — see or lift a HOLD on an Instagram account's scheduled posts — and immediately splits the two modes (status vs. resume). It also names the triggering condition (Meta spam restriction code 4/2207051), so the agent knows exactly what state this tool manages.

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?

It gives explicit when-to-use guidance for resume: only after the user confirms the account holder checked Account Status in the Instagram app. It also names alternative paths that lift the hold (reconnecting Instagram, a successful post), which is real routing guidance rather than inference.

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