Skip to main content
Glama
Hermoso

Hermoso

Official

What to fix next, post by post

diagnose_posts
Read-onlyIdempotent

Analyze recent posts to pinpoint what is wrong—hook, retention, or offer—and identify the next edit to make. Filter by channel; set converting:false when seen posts are not converting.

Instructions

WHAT TO FIX NEXT, post by post — and the tool that fixes it. post_performance tells you which hook is AHEAD; this tells you what is WRONG with a given post and where the next edit goes. Under-distributed is A HOOK PROBLEM (change the opening: mine_angles, then list_hooks, then plan_variations). Seen but not held is A RETENTION PROBLEM (plan_variations to rebuild the middle against the same hook). Seen, held, and still not converting is AN OFFER PROBLEM. FOUR REFUSALS, AND YOU SHOULD REPEAT THEM RATHER THAN PAPER OVER THEM: (1) a post younger than ~24h is TOO EARLY and is never called a failure — it has not had its run; (2) a metric the platform does not publish is UNMEASURED, never zero — Facebook has published no post reach since 2026-06-15, Reddit publishes no impressions, and Google Business publishes nothing per-post at all; (3) below 5 measured posts on a channel there is no baseline of the brand's own, and the ONLY fallback is a published short-video hook floor that is NOT our measured number and does not transfer off TikTok/Instagram/YouTube — it is attributed in the output and you should attribute it too; (4) it does not always find a problem, and 'nothing here needs fixing' is a real answer rather than a failure to look. Hermoso cannot see conversions for an organic post — no channel reports installs or purchases against a post id — so the offer rung runs ONLY when the user tells you they are not converting and you pass converting:false. Print summary verbatim. 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": "diagnose_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many recent posts to diagnose (default 25, max 200). The baseline is always built from EVERY post recorded for the brand, never only these, so a bad month can never become its own definition of normal.
channelNorestrict to one channel: facebook, instagram, threads, x, linkedin, youtube, tiktok, pinterest, bluesky
convertingNopass false ONLY when the user has told you these posts are getting seen and are not converting — it re-reads the ones that are earning their reach as an offer problem instead of a win. Omit when you do not know; we cannot measure it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.519
    • changedInput schema / properties / channel / description
      Previous value: -"restrict to one channel: facebook, instagram, threads, x, linkedin, youtube, tiktok, reddit, pinterest"New value: +"restrict to one channel: facebook, instagram, threads, x, linkedin, youtube, tiktok, pinterest, bluesky"
  2. Addedv0.1.161

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, but the description adds substantive behavior: 0 credits, unmeasured is never zero with dated platform examples (Facebook post reach since 2026-06-15, Reddit impressions, Google Business), a 5-post baseline floor with an attributed external fallback, and the fact that conversions are invisible for organic posts. It also flags which output field to print verbatim.

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 purpose and the routing problem types, and the numbered refusals are scannable. It is dense and long, with some restatement of the title phrase and of the converting rules already in the schema, but nearly every sentence carries decision-relevant content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a diagnostic tool with no output schema, the description covers the interpretive rules an agent needs (unmeasured vs zero, baseline insufficiency, attribution of the external hook floor, and the `summary` field to print verbatim). It stops short of describing the rest of the response shape, which an agent would otherwise have to discover at call time.

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 all three parameters are already documented with their defaults, limits, and the converting rationale — the description mostly restates the converting gate rather than adding new meaning. Baseline 3 applies when the schema carries the parameter burden.

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-and-resource framing ('what is WRONG with a given post and where the next edit goes') and explicitly contrasts with the sibling post_performance ('tells you which hook is AHEAD'). An agent can route between the two without opening either 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 an explicit decision tree: under-distributed → mine_angles/list_hooks/plan_variations, seen-but-not-held → plan_variations, seen-held-not-converting → offer rung with converting:false. It also states the exclusions in the four refusals, including the 24h too-early rule and that 'nothing here needs fixing' is a legitimate outcome.

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