Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find the creators already winning in a niche

find_creators

Identify and rank TikTok, Instagram Reels and YouTube creators for a niche by median views, engagement and frequency, with follower counts and public contact info for outreach.

Instructions

Scan organic TikTok, Instagram Reels and YouTube for a niche across a few query variants, fold the posts into creators, and rank them on median views, engagement rate and how often they show up for that niche; the top rows get follower counts AND public contact info (an Instagram business email / phone / category, the bio link, an email in a TikTok bio) so outreach can start from the result. Real people, not AI actors — for influencer sourcing, UGC casting and partnership prospecting ("who should we send product to?"). About one credit per search call (platforms × queries, default 3 × 3) plus one per enriched profile; repeats inside 20 minutes are free. Then shortlist (save_to_swipefile), check a profile (instagram_profile / fetch_social_data), draft outreach (generate_text), or approve them for Partnership Ads (manage_meta_partnership_creator). marketplace:true also searches Instagram’s creator marketplace (Meta’s own creator directory: followers, badges, marketplace email) for the same niche and returns those rows beside the ranked list.

Input Schema

NameRequiredDescriptionDefault
limitNocreators to return, 1–30 (default 12)
nicheYesproduct category, topic or hashtag — "calorie tracker app", "matcha", "#cleanbeauty"
enrichNofollowers + public contact for the top 3 on TikTok and on Instagram (default true, 1 credit each)
queriesNoquery variants per platform, 1–4 (default 3); each is a paid search call
platformsNodefault all three
marketplaceNoalso search Instagram’s creator marketplace (Meta’s own creator directory, free) for the same niche; needs the Meta connector
minAvgViewsNo
minEngagementNointeractions per view, 0–1 (0.05 = 5%)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.454
    • changedInput schema / properties / enrich / description
      Previous value: -"read follower counts for the top 6 (default true, ~1 credit each)"New value: +"followers + public contact for the top 3 on TikTok and on Instagram (default true, 1 credit each)"
  2. Changed1 schema field changedv0.1.272
    • addedInput schema / properties / marketplace
      Added value: +{
+  "description": "also search Instagram’s creator marketplace (Meta’s own creator directory, free) for the same niche; needs the Meta connector",
+  "type": "boolean"
+}
  3. Addedv0.1.209

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond annotations: approximate credit cost per search call and enriched profile, free repeats within 20 minutes, the default platforms × queries cost model, and the Meta connector prerequisite for marketplace search. It also clarifies enrichment scope and that contact info comes from public/business profile sources.

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?

The purpose is front-loaded and most content is useful, but the first sentence is very long and densely packed with semicolons. It remains readable, though a shorter structured form would improve scanability.

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 an 8-parameter discovery tool with no output schema, the description covers purpose, use cases, cost model, enrichment behavior, marketplace mode, connector prerequisite and follow-on workflow. An agent has enough information to decide whether and how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high, but the description still adds meaningful semantics: it explains the cost implications of platforms and queries, the default enrich behavior and top-3 scope, and what marketplace=true adds and requires. It also explains the kind of contact data enrichment returns, which is more than the schema descriptions provide.

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 combination: scan TikTok, Instagram Reels and YouTube for a niche, aggregate posts into creators, and rank them by median views, engagement rate and niche frequency. It clearly distinguishes this discovery/ranking tool from saved-creator or generic search tools by explaining the creator-folding and outreach-enrichment output.

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?

It names concrete use cases: influencer sourcing, UGC casting, and partnership prospecting, and it gives a follow-on workflow with save_to_swipefile, instagram_profile/fetch_social_data, generate_text and manage_meta_partnership_creator. It does not explicitly say when to prefer this over sibling tools like list_creators or raw search_tiktok/search_instagram, so it falls short of full alternative routing.

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