Skip to main content
Glama
Hermoso

Hermoso

Official

Find the creators already winning in a niche

find_creators

Scan TikTok, Instagram Reels, and YouTube for a niche, rank matching creators by median views, engagement, and niche frequency, then return follower counts and public contact details 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "niche": "<niche>"
    },
    "name": "find_creators"
  }
}

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
get_costNotrue: return the price only; nothing runs or bills
platformsNodefault all three
marketplaceNoalso search Instagram’s creator marketplace (Meta’s own creator directory, free) for the same niche; needs the Meta connector
minAvgViewsNominimum average views per post; creators below this floor are dropped
minEngagementNointeractions per view, 0–1 (0.05 = 5%)
idempotency_keyNochosen once, resent unchanged on retries: the same key never buys twice
expected_creditsNothe get_cost price; refused unbilled if the live price differs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.532
    • addedInput schema / properties / expected_credits
      Added value: +{
      +  "description": "the get_cost price; refused unbilled if the live price differs",
      +  "type": "number"
      +}
    • addedInput schema / properties / get_cost
      Added value: +{
      +  "description": "true: return the price only; nothing runs or bills",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "chosen once, resent unchanged on retries: the same key never buys twice",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.1.465
    • addedInput schema / properties / minAvgViews / description
      Added value: +"minimum average views per post; creators below this floor are dropped"
  3. 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)"
  4. 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"
      +}
  5. Addedv0.1.209

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only flag it as a non-read-only, open-world, non-idempotent call. The description goes well beyond that: it discloses the credit model (one per search call, platforms × queries, default 3 × 3, plus one per enriched profile), that repeats within 20 minutes are free, that idempotency_key prevents double-charging, and that marketplace:true requires the Meta connector.

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?

Purpose is front-loaded in the first clause, followed by output shape, use cases, cost, and next steps in a sensible order. It is a dense, semicolon-heavy run-on with the marketplace caveat appended at the end, which costs it a point on structure even though nearly every sentence carries information.

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 an 11-parameter, no-output-schema tool with thin annotations, the description covers the cost/quota model, enrichment contents, the marketplace branch and the natural next tools. Gaps are minor: no guidance on failure modes (e.g., when contact info is unavailable) or on how many rows enrichment actually touches beyond 'top 3'.

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 still adds meaning the schema doesn't carry: the default 3 × 3 platforms-per-queries cost footprint, which fields enrich populates (business email/phone/category, bio link, TikTok bio email), and the connector prerequisite for marketplace.

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 precise multi-step verb chain — scan organic TikTok/Reels/YouTube for a niche, fold posts into creators, rank on median views/engagement/frequency — which is far more specific than 'find creators'. It also distinguishes the output rows implicitly (ranked list plus enriched top rows) so an agent can tell this apart from a plain listing tool.

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, partnership prospecting, 'who should we send product to?') and lists explicit follow-on tools (save_to_swipefile, instagram_profile/fetch_social_data, generate_text, manage_meta_partnership_creator). What's missing is any when-NOT-to-use guidance or a contrast with the sibling list_creators, so the agent must infer the boundary itself.

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