Skip to main content
Glama
Influship

Influship MCP

Official
by Influship

autocomplete_creators

Read-only

Resolve partial creator handles or names to canonical IDs quickly. Use for fast typeahead-style lookup when a user types a partial name or handle.

Instructions

Autocomplete creator names, usernames, or display names from partial input.

Use this for fast lookup when the user types a partial handle or name and you need to resolve it to canonical creator IDs (e.g., "find @cris" or "who's that fitness coach called Jane?"). Cheap and fast — prefer over search_creators for handle-style queries where the user already knows roughly who they want.

Use get_profile instead when the user gives an exact platform+username pair. Use search_creators for the same fuzzy creator lookup behavior with a less typeahead- specific name. Use semantic_search_creators only for discovery by topic, niche, audience, geography, or content style, not for resolving a known creator.

Examples:

  • User: "Who is that fitness coach called Jane?" -> use this tool.

  • User: "Find @cris..." -> use this tool to resolve the partial handle.

  • User: "Pull @niickjackson on Instagram" -> use get_profile, not this tool.

Returns a short list of matching creators with their IDs, platforms, and display names. Use the IDs returned here as input to get_creator, find_lookalike_creators, or match_creators for downstream operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query (min 2 characters)
platformNoFilter by platform
limitNoMaximum results to return
scopeNoWhich platforms to include in resultsall_platforms

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 indicate safe read operation (readOnlyHint=true, destructiveHint=false). Description adds value by stating 'Cheap and fast' and describing return format ('short list of matching creators with their IDs, platforms, and display names'). No contradictions.

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 core action, usage guidelines, examples, and output. Sentences are efficient and front-loaded. Some slight redundancy (e.g., examples repeat the point), but overall concise for the information provided.

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 presence of annotations, full schema coverage, and output schema, the description covers purpose, usage, alternatives, examples, and output. It is complete for a tool with moderate 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?

Input schema has 100% coverage; every parameter has a description. Description does not add significant parameter details beyond schema, relying on schema to document parameters. Baseline 3 is 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?

Description clearly states 'Autocomplete creator names, usernames, or display names from partial input.' It distinguishes from siblings by explicitly naming alternatives (search_creators, get_profile, semantic_search_creators) and their different 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 ('when the user types a partial handle or name'), when-not-to-use (e.g., 'Use get_profile instead when the user gives an exact platform+username pair'), and names specific alternative tools with rationale.

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