Skip to main content
Glama
Influship

Influship MCP

Official
by Influship

search_creators

Read-onlyIdempotent

Look up creators by name, handle, or partial identifier. Handles exact matches and ambiguous creator searches, returning autocomplete-style or semantic results.

Instructions

Find a creator by name/handle, while preserving legacy semantic creator search.

Use this as the default creator lookup tool when the user gives a creator-ish string but not a canonical creator UUID: a handle, partial handle, display name, creator name, or profile-ish text. This is cheap, fast, and backed by the creator lookup index.

If the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram"), prefer get_profile first because it returns the full platform profile. If you need to resolve a rough creator name or partial handle first, use this tool with query_type: "creator_lookup".

For backward compatibility, this tool still accepts the old semantic-search fields (platforms, follower/engagement filters, creator_kinds) and routes legacy calls to the semantic endpoint unless the query clearly contains a handle/profile URL. For new topical/niche discovery calls such as "fitness creators in NYC" or "vegan recipe creators with high engagement", prefer semantic_search_creators because its name is explicit and less likely to be confused with exact creator lookup.

Examples:

  • User: "Find @cris" -> use this tool with query "cris" and query_type "creator_lookup".

  • User: "Who is that fitness coach called Jane?" -> use this tool with query "Jane" and query_type "creator_lookup".

  • User: "Pull @niickjackson on Instagram" -> use get_profile with platform "instagram" and username "niickjackson".

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

Returns either autocomplete-style creator lookup results or legacy semantic results, depending on routing. Use returned creator IDs with get_creator, find_lookalike_creators, or match_creators; use returned platform usernames with get_profile or get_posts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural-language semantic discovery query by topic, niche, audience, geography, or content style. Do not pass exact handles or usernames here; use get_profile, lookup_profiles, or autocomplete_creators instead.
platformsNoPlatforms to search. Omit for all.
limitNoMaximum results to return.
creator_kindsNoOptional creator kind filter. Omit for no creator-kind filter.
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.
platformNoOptional platform to narrow username matching.
scopeNoWhich linked platforms to include in each lookup result.all_platforms
query_typeNoUse creator_lookup for specific names/handles and semantic_discovery for topical/niche discovery. Auto routes exact handles and profile URLs to lookup, and keeps legacy semantic-search behavior otherwise.auto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds that it is 'cheap, fast' and explains legacy routing behavior without contradiction.

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?

Well-structured with front-loaded purpose, clear examples, and logical flow. Slightly long but justified given complexity. No wasted sentences.

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?

Fully covers usage, alternatives, legacy behavior, and parameter guidance. With 12 parameters, 100% schema coverage, and output schema present, the description is sufficiently complete.

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 baseline is 3. Description adds value by explaining how to use query_type (creator_lookup vs semantic_discovery) and providing usage context for backward-compatible parameters.

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?

Clearly states 'Find a creator by name/handle' and 'preserving legacy semantic creator search.' Distinguishes from siblings like get_profile and semantic_search_creators by specific use cases.

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?

Provides explicit when-to-use vs. when-not-to-use with concrete examples, including preferred alternatives (get_profile for exact handles, semantic_search_creators for niche discovery).

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