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

See what social posts are queued to publish and what already went out, including per-channel success or failure; inspect, filter, or expand results.

Instructions

Use this when the user asks what is scheduled, what already posted, or whether a post went out. 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

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 cover readOnly/idempotent/non-destructive, and the description adds genuinely non-obvious behavior: the list is truncated (next 25 queued, last 15 fired) with captions shortened, past items are rebuilt from published-post records rather than job runs, and each item reports per-channel verdicts so partial failures aren't masked. Cost ('0 credits') and the full-detail escape hatch via `id` round it out.

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?

Front-loaded with the use case and the most decision-relevant facts (compactness, per-channel outcomes) before the parameter walkthrough. Dense but mostly earns its length; the second sentence lightly restates the first, and the ALL-CAPS emphasis is stylistically heavy, costing a point.

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 5-param read tool with no output schema, the description covers return shape (compact list, per-channel rows, truncated captions), default limits, filtering options, and the full-detail mode, while annotations carry the safety profile. Nothing needed to invoke it correctly is missing.

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% and the schema descriptions are already rich, so the baseline is 3. The description adds value beyond the schema by explaining the workflow meaning of `id` (returns the post in full, required before reschedule_post) and framing `channel`/`upcoming`/`fired` as filters/expanders rather than raw numbers.

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 verb+resource ('list' scheduled and past posts) and immediately clarifies scope: queued items plus fired items, per-channel outcomes, one row per channel. It distinguishes itself from list_jobs explicitly ('they are not job runs'), so an agent can separate the two without opening schemas.

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?

Opens with an explicit trigger ('Use this when the user asks what is scheduled, what already posted, or whether a post went out') and names the alternative for job runs (list_jobs). It also ties the `id` parameter to a downstream workflow ('which you need before reschedule_post replaces a caption map'), giving concrete when-to-use context.

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