Skip to main content
Glama
Hermoso

Hermoso

Official

Autopilot posting status

get_post_refill
Read-onlyIdempotent

Shows autopilot posting status, mode, channels, daily cost, next run, queued posts, pending drafts, and review notes so you can see what is waiting and what cannot post.

Instructions

Show AUTOPILOT POSTING (autoposting, the posting refill) for this profile — "is autopilot on?", "what is waiting for review?": whether it is on, its mode (review = each batch of fresh posts waits as drafts for approval; auto = fresh posts are scheduled straight away), WHICH CHANNELS it posts to with each one’s posts per day and posting times, roughly what it costs a day, when it next runs, how many posts are queued, the DRAFTS waiting for approval (id, time, channels, caption, the new image or video), and the notes it learned from reviews. It also names the channels that CANNOT be posted to and why. On the Free plan, paidOnly is true and note explains the status. Read-only, 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": "get_post_refill"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.161

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered; the description contributes real additional behavior – the review vs auto mode semantics, that unpostable channels are named with reasons, and that on the Free plan paidOnly is true with an explanatory note. It does not cover failure modes (e.g. autopilot never configured) or response shape as JSON, which keeps it off a 5.

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

Conciseness3/5

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

The description is front-loaded with the core purpose, which is good, but it then unspools into one very long sentence enumerating every returned field, with ALL-CAPS emphasis and parenthetical asides. The content is useful given there is no output schema, but a short structured list would communicate the same information far more scannably.

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?

With no output schema, the description carries the full return-value burden and does so thoroughly: mode, per-channel cadence, cost, next run, queue depth, draft contents, learned notes, and blocked channels. What is missing is only marginal – error/empty states and how the profile is bound.

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?

There are zero parameters, so per the rubric this takes the baseline 4. The only semantic hint is that it operates implicitly on "this profile," which is all that is needed.

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?

"Show AUTOPILOT POSTING ... for this profile" gives a specific verb and resource, and the enumerated contents (mode, channels, cost, queue, drafts, notes) make the scope unmistakable. It stops short of naming the siblings set_post_refill and run_post_refill, so the agent must infer that this is the read/status counterpart rather than being told directly.

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

Usage Guidelines4/5

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

The quoted user questions ("is autopilot on?", "what is waiting for review?") are concrete usage triggers that map well to real intents. However, there are no exclusions and no explicit pointer to set_post_refill (to change it) or run_post_refill (to trigger it), which are the obvious alternatives for an agent that lands on the wrong tool.

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