Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List scheduled and past posts

list_scheduled
Read-only

Show scheduled and published social posts with per-channel results (e.g., Instagram published, TikTok failed). Filter by post ID or channel; read-only, uses 0 credits.

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
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. 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"
+}
  2. Addedv0.1.161

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds substantial non-annotation context: per-channel outcome reporting (Instagram published, TikTok failed), compact listing limits (next 25 queued, last 15 fired, shortened captions), and '0 credits'. It doesn't detail pagination edge cases, but for a read-only list tool this is rich beyond the annotations.

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

Conciseness5/5

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

Front-loads what is listed, then the per-channel outcome distinction, the alternative (list_jobs) and the compact limits, then parameter guidance and the read-only crediting. Every sentence earns its place; no redundancy.

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 read-only list tool with no output schema, annotations covering safety and a compact listing with clear defaults, the description supplies everything an agent needs to call it correctly: scope, defaults, override parameters, the downstream dependency on id before reschedule_post, and cost. Nothing material 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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the intent of `id` (returns one post in full, needed before reschedule_post) and the combined effect of `upcoming`/`fired` (defaults 25/15, captions shortened), reinforcing the defaults and the 'one reply' compaction rationale.

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 (list/show) and resource (queued and already-fired posts), and explicitly distinguishes itself from the sibling list_jobs ('they are not job runs (use list_jobs for those)'). It also clarifies it differs from list_published_posts by noting past items are rebuilt from published-post records, one row per channel.

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?

Explicitly states when to use alternatives: use list_jobs for job runs, and pass `id` for a single full post 'which you need before reschedule_post replaces a caption map'. This ties usage to a concrete downstream workflow, leaving nothing to 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