Skip to main content
Glama
Hermoso

Hermoso

Official

List what this brand has published

list_published_posts
Read-onlyIdempotent

Retrieve a brand's full publishing history, newest first — channel, permalink, caption, format, hook, subject, and engagement — with cursor paging for older posts. Read-only, no credits.

Instructions

List every post Hermoso has recorded publishing for this brand, newest first, across all channels — channel, permalink, caption, format, the HOOK and SUBJECT it was written to, and its measured engagement. The WHOLE history, no cap: pass the reply's nextCursor as cursor for older posts. Each row says how it was recorded: 'captured' (written at publish time — the hook is what the author intended) or 'backfilled' (reconstructed from the platform afterwards). A dash for engagement means the platform reported no number — NOT zero. Read-only, 0 credits.

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

Input Schema

NameRequiredDescriptionDefault
brandNoWHICH PROFILE the post lives in — id or exact name from list_brands (a shared workspace: its profile id). Needed when it was published in a profile this connection is not pinned to; applies to THIS CALL ONLY. A name that matches no profile, or two, is REFUSED and nothing is done.
limitNomax posts (default 50, max 200), newest first
cursorNonextCursor from a previous reply: the next, older page
channelNofilter to one channel: facebook, instagram, threads, x, linkedin, youtube, tiktok, pinterest, bluesky, google_business

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.519
    • changedInput schema / properties / channel / description
      Previous value: -"filter to one channel: facebook, instagram, threads, x, linkedin, youtube, tiktok, reddit, pinterest, google_business"New value: +"filter to one channel: facebook, instagram, threads, x, linkedin, youtube, tiktok, pinterest, bluesky, google_business"
  2. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND the post lives in — id or exact name from list_brands (a shared workspace: its profile id). Needed when it was published in a brand this connection is not pinned to; applies to THIS CALL ONLY. A name that matches no brand, or two, is REFUSED and nothing is done."New value: +"WHICH PROFILE the post lives in — id or exact name from list_brands (a shared workspace: its profile id). Needed when it was published in a profile this connection is not pinned to; applies to THIS CALL ONLY. A name that matches no profile, or two, is REFUSED and nothing is done."
  3. Changed1 schema field changedv0.1.320
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND the post lives in — the id or exact name from list_brands (a workspace shared with you: its profile id). Needed when it was published in a brand this connection is not pinned to: a post you can CREATE in a brand is manageable there too, for THIS CALL ONLY, without switching the connection. A name that matches no brand, or two, is REFUSED and nothing is done."New value: +"WHICH BRAND the post lives in — id or exact name from list_brands (a shared workspace: its profile id). Needed when it was published in a brand this connection is not pinned to; applies to THIS CALL ONLY. A name that matches no brand, or two, is REFUSED and nothing is done."
  4. Changed1 schema field changedv0.1.281
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "nextCursor from a previous reply: the next, older page",
      +  "type": "string"
      +}
  5. Changed1 schema field changedv0.1.272
    • addedInput schema / properties / brand
      Added value: +{
      +  "description": "WHICH BRAND the post lives in — the id or exact name from list_brands (a workspace shared with you: its profile id). Needed when it was published in a brand this connection is not pinned to: a post you can CREATE in a brand is manageable there too, for THIS CALL ONLY, without switching the connection. A name that matches no brand, or two, is REFUSED and nothing is done.",
      +  "type": "string"
      +}
  6. Addedv0.1.161

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description still adds genuine context by stating there is no cap and how pagination terminates via nextCursor. It also discloses the 'captured' vs 'backfilled' provenance semantics and warns that a dash for engagement means unreported, not zero — real behavioral detail an agent could otherwise misread. The 'read-only, 0 credits' claim mostly restates the annotations, which keeps it from 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.

Conciseness4/5

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

Effectively two front-loaded sentences: scope and returned columns first, then pagination and provenance semantics. Nearly every clause earns its place, though the dense field enumeration and all-caps emphasis (WHOLE, HOOK, SUBJECT, NOT) push it toward the verbose end for a read-only list tool.

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?

There is no output schema, so the description carries the return-shape burden and does: it lists the fields per row, explains pagination to exhaustion, interprets the provenance flag, and disambiguates a dash value. For a four-parameter read-only listing tool with full schema coverage and annotations, nothing an agent needs in order to call or interpret it is missing.

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 description coverage is 100%, so brand, limit, cursor, and channel are already documented, and the description only reinforces the cursor loop with 'pass the reply's nextCursor as `cursor` for older posts.' It adds no channel-enum detail, default/max limits, or brand-resolution guidance beyond what the schema provides, so the baseline 3 holds.

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?

"List every post Hermoso has recorded publishing for this brand, newest first, across all channels" gives a precise verb, resource, ordering, and scope, and then enumerates the returned fields (channel, permalink, caption, format, hook, subject, engagement). That distinguishes it from retrieval-style siblings like search_posts, list_meta_posts, and post_performance without the agent needing to open a schema.

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

Usage Guidelines3/5

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

Usage context is implied and partially stated: it is the record of what was actually published, and the cursor sentence tells the agent how to walk older pages. However, it never names an alternative (search_posts for keyword discovery, post_performance for metric deep-dives, diagnose_posts for analysis) or states an exclusion, so an agent must infer routing from the name and description alone.

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