Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Import a channel’s past posts

backfill_posts
Idempotent

Import a brand's past social channel posts into the performance record so hook analysis draws on history. Dry-run first, then confirm to import and resume with a cursor.

Instructions

Import this brand's PAST posts from a channel into the performance record, so 'which hook works' can draw on history rather than only on what was published since Hermoso started recording. Supports facebook, instagram, threads, youtube, tiktok, pinterest and bluesky; the others say plainly why they cannot (LinkedIn and Reddit have no enumerate-my-posts endpoint on our grant, X bills per read so it is excluded from bulk import, Google Business has had no per-post insights since 2023, and Telegram's Bot API cannot read a chat's past messages at all — nothing published before Hermoso is recoverable through a bot token). BOUNDED, RESUMABLE AND QUOTED: it runs as a DRY RUN by default and tells you how many posts it found and what reading them will cost — pass confirm:true to import, and pass the returned cursor to continue. AN IMPORTED POST IS WEAKER EVIDENCE THAN A RECORDED ONE and is labelled 'backfilled': its hook is recovered ONLY where the post matches a Hermoso creation by asset or caption. A post made outside Hermoso stays UNATTRIBUTED — it counts toward channel and format totals but never votes on which hook works. Never guess a hook from a caption. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNohow many posts this page (default 50, max 200)
cursorNoresume from a previous run
channelYeswhich channel to import from
confirmNoactually import — omit for a dry run that only quotes the cost
accountRefNowhich Page / account, when the profile has more than one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / accountRef / description
      Previous value: -"which Page / account, when the brand has more than one"New value: +"which Page / account, when the profile has more than one"
  2. Addedv0.1.161

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the mutation/idempotency profile is known. The description adds genuinely useful context beyond that: dry-run default with cost quoting, the resumable cursor, the 'backfilled' weaker-evidence labeling, and the unattributed-post rule. It is strong on behavioral nuance, though the 'Free' claim and evidence semantics are the main additions over structured fields.

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-loads the core action and destination before channel support and mechanics, and the ordering is logical. It is dense and lengthy, but the length is largely justified by the breadth of channel-specific exclusions, so little is genuinely wasted.

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 mutation tool with five params and no output schema, the description covers the essentials an agent needs: return-relevant info (count and cost), dry-run/confirm semantics, resumability, and the evidence-strength and attribution caveats that affect downstream use.

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 all five parameters are already documented. The description ties confirm and cursor into a coherent two-step resumable workflow (quote cost, then confirm, then continue via cursor), adding flow-level meaning beyond the per-field descriptions, though it largely reinforces what the schema already states.

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 (import) and resource (this brand's past posts from a channel) plus the destination (the performance record) and the reason (so hook analysis can draw on history). This clearly distinguishes it from siblings like list_published_posts, collect_post_metrics, or search_posts.

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?

Enumerates which channels are supported and, crucially, explains for each unsupported channel (LinkedIn, Reddit, X, Google Business, Telegram) why import is impossible. It also specifies the dry-run-by-default flow and how to proceed (confirm:true, then cursor), 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