Influship

autocomplete_creators

Read-only

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

Name	Required	Description	Default
`q`	Yes	Search query (min 2 characters)
`limit`	No	Maximum results to return
`scope`	No	Which platforms to include in results	all_platforms
`platform`	No	Filter by platform

Output Schema

Name	Required	Description	Default
`ok`	No
`data`	No
`count`	No
`results`	No
`has_more`	No
`not_found`	No
`next_cursor`	No
`suggested_followups`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 23, 2026

addedInput schema / $ref

Added value: +"#/definitions/AutocompleteQuery"

addedInput schema / definitions / AutocompleteQuery

Added value: +{
+  "properties": {
+    "limit": {
+      "default": 5,
+      "description": "Maximum results to return",
+      "example": 5,
+      "maximum": 50,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "platform": {
+      "allOf": [
+        {
+          "$ref": "#/definitions/Platform"
+        }
+      ],
+      "description": "Filter by platform"
+    },
+    "q": {
+      "description": "Search query (min 2 characters)",
+      "example": "fitness",
+      "maxLength": 100,
+      "minLength": 2,
+      "type": "string"
+    },
+    "scope": {
+      "default": "all_platforms",
+      "description": "Which platforms to include in results",
+      "enum": [
+        "creator_only",
+        "matched_platforms",
+        "all_platforms"
+      ],
+      "example": "all_platforms",
+      "type": "string"
+    }
+  },
+  "required": [
+    "q"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / next_cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / next_cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedMay 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds real value by characterizing cost/latency ('cheap and fast') and by explaining that returned IDs feed downstream tools like get_creator and match_creators. Describing the return fields is somewhat redundant given an output schema exists.

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?

Content is front-loaded with the purpose, then routing guidance, then examples, so an agent can stop reading early. It runs longer than necessary, and the clause about search_creators having 'a less typeahead-specific name' is slightly muddled relative to the earlier framing.

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?

With annotations covering safety and an output schema covering returns, the description supplies the remaining decision-critical context: cost profile, alternatives, and ID chaining for downstream calls. Only the scope enum semantics remain undocumented anywhere in the definition.

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 q, limit, scope, and platform are all documented in the schema; the description adds only that q matches names, usernames, and display names via partial input. The 'scope' enum (creator_only / matched_platforms / all_platforms) is the one genuinely ambiguous parameter and is left unexplained in the description.

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?

States a specific verb and resource ('Autocomplete creator names, usernames, or display names from partial input') and immediately differentiates itself from the lookalike siblings that could be confused with it. The first sentence alone lets an agent distinguish this from search_creators or get_profile.

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 enumerates when to use this tool ('user types a partial handle or name', 'who's that fitness coach called Jane?') and when not to, naming concrete alternatives: get_profile for exact platform+username, search_creators for fuzzy lookup, semantic_search_creators for topic/geography/style discovery. The three worked examples reinforce the routing rules.

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

All Influship tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.