Skip to main content
Glama
Influship

Influship MCP

Official
by Influship

find_lookalike_creators

Read-only

Find creators similar to known seed creators by blending profile, visual style, and fact embeddings. Specify seeds by UUID or platform username to receive a ranked list of lookalikes with optional follower and engagement filters.

Instructions

Find creators SIMILAR to one or more seed creators.

Use this when the user already knows a creator they like and wants more like them (e.g., "find creators like @therock", "find more creators like these three I just booked"). Seeds are blended via creator-profile + visual-style + fact embeddings to surface similar accounts.

Seeds are passed in seed_creator_ids (canonical UUIDs) and/or seed_profiles (platform + username; resolve handles via autocomplete_creators first if needed). Returns a ranked list of similar creators with scores. limit caps results (default 25, max 100). Use the flat follower, engagement-rate, and verified fields to constrain results.

Use semantic_search_creators instead when you have a topic/niche but no seed. Use match_creators when you have specific candidates and want to score their fit against a brief.

Examples:

  • User: "Find creators like @niickjackson on Instagram" -> use this tool with seed_profiles: [{ platform: "instagram", username: "niickjackson" }].

  • User: "Find news creators with 1M+ followers" -> use semantic_search_creators, not this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seed_creator_idsNoSeed creators identified by canonical Influship creator UUID.
seed_profilesNoSeed creators identified by platform and username.
limitNoMaximum results to return.
cursorNoPagination cursor from a previous response.
min_followersNoMinimum follower count.
max_followersNoMaximum follower count.
min_engagement_rateNoMinimum engagement rate as a percentage from 0 to 100.
max_engagement_rateNoMaximum engagement rate as a percentage from 0 to 100.
verifiedNoWhen set, only return verified or unverified creators.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
resultsNo
countNo
okNo
not_foundNo
has_moreNo
next_cursorNo
suggested_followupsNo
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, but description adds context beyond annotations: explains how seeds are blended (embeddings), returns ranked list with scores, and mentions pagination via cursor.

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?

Description is front-loaded with bold purpose, uses bullet points and examples. It is reasonably concise, with each sentence adding value. Slightly long but appropriate for a complex tool.

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?

Given the tool has an output schema, description does not need to document return values. It covers usage context, alternatives, blending method, and pagination. Complete for a tool of this complexity.

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 coverage is 100%, so baseline 3 is appropriate. Description adds some context for seed_profiles (resolve handles via autocomplete_creators) but does not elaborate on all parameters beyond schema definitions.

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?

Description clearly states the tool finds creators similar to seed creators. It uses a specific verb and resource, and distinguishes from siblings by naming alternatives and giving examples.

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 says when to use (user knows a creator and wants similar) and when not to use (topic/no seed -> semantic_search_creators; specific candidates -> match_creators). Provides concrete examples.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Influship/influship-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server