Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Reddit

search_reddit
Read-only

Dig into Reddit conversations by keyword to uncover customers' exact pain points and objections, then turn their own words into ad hooks and copy.

Instructions

Reddit keyword search (/v1/reddit/search, top-ranked) — a goldmine for the customer's OWN words (pain points, objections, language) to mine into ad hooks and copy. Returns compact JSON {desc (title+selftext), subreddit, upvotes, comments, link} per post. Spends about a credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomax posts returned (1–25, default 8)
queryYeswhat to search Reddit for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "found": {
-      "description": "total posts found",
-      "type": "number"
-    },
-    "posts": {
-      "description": "the compact post objects ({desc, subreddit, upvotes, comments, link})",
-      "items": {},
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds valuable behavioral context on top: it spends about a credit, returns compact JSON, and describes the exact per-post shape. It does not disclose rate limits or auth requirements, but the key cost and return behavior are covered.

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?

Two tight sentences front-load the endpoint and use case, then deliver return format and cost without filler. Every element earns its place; the JSON return shape is specified compactly rather than in prose.

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?

With no output schema, the description compensates by describing the return object fields. It also covers the cost implication, which is important for an agent deciding whether to call the tool. It could add more detail on result ordering or ranking, but the essential operational information is present.

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 the baseline is 3. The description adds extra meaning by framing the query as a search for the customer's own words and objections, which goes beyond the schema's generic 'what to search Reddit for.' This helps the agent craft more effective queries.

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?

The description clearly states the tool performs a Reddit keyword search and identifies the exact endpoint. It also explains the intended output—compact JSON with desc, subreddit, upvotes, comments, and link—and frames the use case around mining customer language, which helps distinguish it from other platform-specific search tools.

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

Usage Guidelines4/5

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

The description gives clear context for when to use this tool: when you need the customer's own words, pain points, and objections for ad hooks and copy. It does not explicitly name alternatives or state when not to use it, but the intended use case is clear enough for an agent to route appropriately among sibling search tools.

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