Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Instagram

search_instagram

Search Instagram Reels by keyword to retrieve reels ranked by plays, returning author, handle, likes, link, and cover in compact JSON.

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 openWorldHint=true and readOnlyHint=false, and the description usefully explains the non-read-only nature by stating 'Spends about a credit'. It also discloses the compact return shape and that results are ranked by plays. It does not mention rate limits or search syntax limits, so it stops short of 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.

Conciseness5/5

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

A single dense passage with zero filler — purpose first, then the disambiguation rule, return shape, and cost. Every clause earns its place and nothing is front-loaded incorrectly.

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?

No output schema exists, and the description compensates by listing the returned fields ({desc, author, handle, plays, likes, link, cover}) and the ranking. Combined with the credit cost and alternative routing, an agent has everything needed to call it correctly.

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% (both query and limit documented, including the 1-25 range and default 8), so the schema carries parameter semantics. The description adds no syntax, format, or operator guidance beyond what the schema already provides, making the baseline 3 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?

States a specific verb+resource+scope: 'Organic Instagram REELS keyword search'. It further differentiates by naming the endpoint surface and clarifying that profile/hashtag pulls are a different operation, so an agent can separate it from fetch_social_data and the other search_* tools without opening 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 Guidelines5/5

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

Explicitly states the when: 'our only IG keyword surface', and the when-not plus alternative: 'profile/hashtag pulls go through fetch_social_data with a handle'. This is exactly the routing guidance an agent needs versus siblings.

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