Skip to main content
Glama

AIsa Sales

by one.aisa
OverviewDiscussionsAdmin

Similar Creators

post_waveinflu_similar_creators
Read-onlyIdempotent

Finds creators similar to a seed account on Instagram, TikTok, or YouTube. platform and target_account are required; add limit (1–100, default 40) and optional filters (regions, languages, follower and play-count ranges, gender, ethnicity, creator type, face visibility, workspace dedup). Each match returns a rich profile: biography, email, followerCount, averagePlayCount / medianPlayCount, averageEngagementRate / medianEngagementRate, plus AI-inferred gender, ageRange, ethnicity, faceVisibility, accountPositioning tags, and an aiDescription, with a relevance score. Results are sorted by score descending. Billing is per delivered creator (data.count).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of creators to return. Default 40, range 1–100. Caps the billed count.
filtersNoOptional filters applied before matching. All fields are optional.
platformYesTarget platform.
target_accountYesSeed account: a creator handle (with or without @) or profile URL to find similar creators for.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changed
    • removedInput schema / properties / contentDirection
      Removed value: -{
-  "description": "Natural-language description of the creator type you are looking for. Max 800 characters.",
-  "example": "consumer tech creators covering AI apps, Android phones, productivity gadgets, and honest product reviews",
-  "maxLength": 800,
-  "type": "string"
-}
    • addedInput schema / properties / filters / description
      Added value: +"Optional filters applied before matching. All fields are optional."
    • addedInput schema / properties / filters / properties / creatorTypes
      Added value: +{
+  "description": "Creator account types, e.g. [\"individual\", \"brand\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / filters / properties / ethnicities
      Added value: +{
+  "description": "Inferred creator ethnicities.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / filters / properties / faceVisibilities
      Added value: +{
+  "description": "Face-visibility classifications, e.g. [\"clear_face\", \"mixed\", \"no_face\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / filters / properties / genders
      Added value: +{
+  "description": "Inferred creator genders, e.g. [\"female\", \"male\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / filters / properties / maxPlayCount
      Added value: +{
+  "description": "Maximum play / view count, measured by `playCountMetric`.",
+  "type": "number"
+}
    • removedInput schema / properties / filters / properties / maxVideosAverageViews
      Removed value: -{
-  "description": "Maximum average view / play count.",
-  "type": "number"
-}
    • addedInput schema / properties / filters / properties / minPlayCount
      Added value: +{
+  "description": "Minimum play / view count, measured by `playCountMetric`.",
+  "type": "number"
+}
    • removedInput schema / properties / filters / properties / minVideosAverageViews
      Removed value: -{
-  "description": "Minimum average view / play count.",
-  "type": "number"
-}
    • addedInput schema / properties / filters / properties / playCountMetric
      Added value: +{
+  "description": "Whether `minPlayCount` / `maxPlayCount` are compared against the median or the average play count.",
+  "enum": [
+    "median",
+    "average"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / filters / properties / regions / description
      Previous value: -"Creator regions, e.g. [\"US\", \"GB\", \"JP\"]."New value: +"Creator regions (ISO country codes), e.g. [\"US\", \"GB\", \"JP\"]."
    • addedInput schema / properties / filters / properties / workspaceDeduplicationEnabled
      Added value: +{
+  "description": "When true, creators already saved in your workspace are excluded from the results.",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / default
      Previous value: -25New value: +40
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of creators to return. Default 25, range 1–100."New value: +"Maximum number of creators to return. Default 40, range 1–100. Caps the billed count."
    • changedInput schema / properties / platform / description
      Previous value: -"Target platform. Currently supports youtube and tiktok."New value: +"Target platform."
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "youtube",
-  "tiktok"
-]New value: +[
+  "instagram",
+  "tiktok",
+  "youtube"
+]
    • changedInput schema / properties / platform / example
      Previous value: -"youtube"New value: +"instagram"
    • removedInput schema / properties / seedProfileUrl
      Removed value: -{
-  "description": "YouTube or TikTok creator profile URL as the seed for matching.",
-  "example": "https://www.youtube.com/@mkbhd",
-  "type": "string"
-}
    • addedInput schema / properties / target_account
      Added value: +{
+  "description": "Seed account: a creator handle (with or without @) or profile URL to find similar creators for.",
+  "example": "@onkimia",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "platform"
-]New value: +[
+  "platform",
+  "target_account"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world). The description adds genuinely non-obvious behavior: results are sorted by relevance score descending, and billing is per delivered creator tied to data.count, which is important cost context. It does not mention rate limits or error behavior, but the additions go meaningfully beyond the annotations.

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?

Front-loaded with the purpose, then parameters, then return shape in three dense sentences with no filler. The enumerated field list is somewhat long and partly duplicates the output schema, which costs a bit of efficiency.

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?

Covers purpose, required inputs, filter knobs, sorting, and billing, which is more than enough for a read-only search with a full output schema. The return-field enumeration is redundant given the output schema exists, but nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the baseline is 3. The description goes further by summarizing limit's default and range and by grouping the filter families (regions, languages, follower/play-count ranges, gender, ethnicity, creator type, face visibility, workspace dedup) into a scannable overview that helps the agent plan a call without reading the nested schema.

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 (finds creators similar to a seed account) and names all three supported platforms, so the agent immediately knows the scope. It is clearly distinguishable from the Apollo/Similarweb siblings and from the other waveinflu tools (ai_search, email_lookup).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the purpose statement (find lookalike creators given a seed), and required vs optional inputs are spelled out. However, it never says when to prefer this over the sibling post_waveinflu_ai_search, nor any when-not conditions, so the routing guidance is left to inference.

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

All AIsa Sales toolsInspect
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.

Resources