Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Instagram

search_instagram
Read-only

Search Instagram Reels by keyword and retrieve ranked results with author, plays, likes, and link. Use it to research organic reel content and winning angles for marketing campaigns.

Instructions

Organic Instagram REELS keyword search (/v2/instagram/reels/search — our only IG keyword surface; profile/hashtag pulls go through fetch_social_data with a handle). Returns compact JSON {desc, author, handle, plays, likes, link, cover} per reel, ranked by plays. Spends about a credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomax reels returned (1–25, default 8)
queryYeskeyword to search reels 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 reels found",
-      "type": "number"
-    },
-    "reels": {
-      "description": "the compact reel objects ({desc, author, handle, plays, likes, link, cover}), ranked by plays",
-      "items": {},
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds further behavioral context: it returns reels ranked by plays, spends about a credit, and returns a compact JSON structure with specific fields. This goes beyond the annotations without contradicting them.

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?

The description is compact but packs in the endpoint, scope, alternative routing, return shape, ranking behavior, and credit cost. Every clause provides actionable information, and the key differentiator is front-loaded.

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 simple two-parameter read-only search tool with no output schema, the description is complete: it covers what the tool returns, how results are ordered, what it costs, and how it relates to sibling and alternative tools. Nothing necessary for correct invocation 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 the schema already documents both query and limit. The description adds the useful detail that results are ranked by plays and the response shape, but it doesn't materially add to the parameter semantics themselves, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Organic Instagram REELS keyword search' with the exact endpoint. It also distinguishes itself from sibling tools by clarifying it is the only IG keyword surface and that profile/hashtag pulls go through fetch_social_data.

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?

The description explicitly names the alternative path for profile/hashtag pulls, telling the agent exactly when to use this tool versus fetch_social_data. This is clear routing guidance that prevents misuse.

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