Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List scheduled and past posts

list_scheduled
Read-onlyIdempotent

View queued and already-fired social posts with per-channel publish outcomes, filter by channel or brand, or inspect one post in full. Read-only; helps confirm what is scheduled and what succeeded.

Instructions

Show what is queued to post and what already went out. Each fired item reports PER-CHANNEL outcomes, so you can see that (say) Instagram published and TikTok failed on the same item rather than a single misleading verdict. Past items are rebuilt from published-post records, one row per channel; they are not job runs (use list_jobs for those). THE LIST IS COMPACT so it fits in one reply: the next 25 queued and the last 15 fired, captions shortened. Pass id for ONE post in full (every caption and setting, which you need before reschedule_post replaces a caption map), channel to filter, or upcoming / fired for more rows. Read-only, 0 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoone post id from this list: returns that post in full, every caption and setting included
brandNoWHICH PROFILE to list — the id or exact name from list_brands. Needed when the post lives in a profile this connection is not pinned to: a post you can CREATE in a profile must be manageable there too, without switching the whole connection. A name that matches no profile, or two, is REFUSED.
firedNohow many already-fired posts to list, most recent last (default 15, max 200)
channelNoonly posts that include this channel, e.g. "pinterest" or "x"
upcomingNohow many queued posts to list, soonest first (default 25, max 200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND to list — the id or exact name from list_brands. Needed when the post lives in a brand this connection is not pinned to: a post you can CREATE in a brand must be manageable there too, without switching the whole connection. A name that matches no brand, or two, is REFUSED."New value: +"WHICH PROFILE to list — the id or exact name from list_brands. Needed when the post lives in a profile this connection is not pinned to: a post you can CREATE in a profile must be manageable there too, without switching the whole connection. A name that matches no profile, or two, is REFUSED."
  2. Changed1 schema field changedv0.1.251
    • addedInput schema / properties / brand
      Added value: +{
+  "description": "WHICH BRAND to list — the id or exact name from list_brands. Needed when the post lives in a brand this connection is not pinned to: a post you can CREATE in a brand must be manageable there too, without switching the whole connection. A name that matches no brand, or two, is REFUSED.",
+  "type": "string"
+}
  3. Changed4 schema fields changedv0.1.243
    • addedInput schema / properties / channel
      Added value: +{
+  "description": "only posts that include this channel, e.g. \"pinterest\" or \"x\"",
+  "type": "string"
+}
    • addedInput schema / properties / fired
      Added value: +{
+  "description": "how many already-fired posts to list, most recent last (default 15, max 200)",
+  "type": "number"
+}
    • addedInput schema / properties / id
      Added value: +{
+  "description": "one post id from this list: returns that post in full, every caption and setting included",
+  "type": "string"
+}
    • addedInput schema / properties / upcoming
      Added value: +{
+  "description": "how many queued posts to list, soonest first (default 25, max 200)",
+  "type": "number"
+}
  4. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, open-world read, but the description adds substantive behavior the annotations cannot: per-channel outcomes (Instagram published / TikTok failed on one item), past rows being rebuilt from published-post records at one row per channel, the compact default window (next 25 queued, last 15 fired) with shortened captions, and the cost profile ('Read-only, 0 credits').

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 scoping constraint and the list_jobs disambiguation are front-loaded, and the compactness/cost facts arrive in the last third where they belong. It is dense and parenthetical-heavy ('(say)', '(use list_jobs for those)'), which slightly taxes readability, but every sentence carries distinct information.

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?

With no output schema, the description carries the return-shape burden and does so: per-channel outcome rows, one row per channel for past items, and an explicit statement that the default list is truncated and captions are shortened. An agent knows both what it will get and when it must request the full record.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema: why `id` matters (full captions and settings are needed before reschedule_post replaces a caption map) and why `brand` exists (managing a post in a profile the connection is not pinned to). It does not restate the numeric defaults/maxima that the schema already documents.

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?

Opens with a specific verb+resource and scope: 'Show what is queued to post and what already went out.' It explicitly differentiates itself from a closely-named sibling by stating past items 'are not job runs (use list_jobs for those),' so an agent can route correctly 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?

Gives explicit routing rules: use list_jobs for job runs, pass `id` for a single post in full, `channel` to filter, and `upcoming`/`fired` to widen the window. It also names the downstream dependency ('which you need before reschedule_post replaces a caption map') and the upstream source for brand values (list_brands).

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