Skip to main content
Glama

Search influencers

search_influencers
Read-only

Search the INFLUENCER directory (the website's /influence page): YouTube channels and Instagram accounts with audience size and activity. One row = one creator. platform is required: youtube or instagram. Filters: q (name / topic words), country (ISO-2 code such as US, or the English country name as the directory writes it, comma separated), category and niche (YouTube only; the directory's own labels, exact match, comma separated — YouTube category examples: Gaming, Music, Education, Comedy, Sports, 'Beauty & Makeup', 'Tech, AI & Software', 'Finance & Cryptocurrency', 'Food, Drink & Cooking', Fitness, 'Travel & Events'; when unsure of a label search by q instead), followers_min / followers_max (subscribers / followers), last_video_days (creators active in the last N days: last video on YouTube, last post on Instagram), has_email (true = creators with an email in the directory), sort (YouTube: followers default, views, videos, last_video; Instagram: followers only). Instagram rows carry the account handle in username and have no niche, avg_views or lang_hint. Rows: slug, name, platform, followers, avg_views (YouTube: average views per video), count_views (YouTube: total views), media_count (videos / posts), country, niche, category, lang_hint (YouTube writing-script hint such as 'latin' — NOT a language), last_video_at / last_post_at, has_email, url (YouTube creator page on spytrend.com). CONTACTS ARE NEVER RETURNED: no emails, phones, websites, social links or bios — has_email is only a yes/no. total_estimate is an ESTIMATE scaled to the directory size, never an exact count. Pagination: limit is at most 10; offset must be a multiple of limit. Callers without an Influence subscription get subscription_locked=true: only the first row carries statistics, the others are name/country/niche teasers (stats_hidden=true, not charged) and there is no second page. QUOTA: 1 MCP credit per row that carries statistics; teaser rows and short pages are refunded. PRICING: price × number of filters set (min 1), on paid plans ×1 after 500 MCP credits/month; one-time consent via accept_pricing_terms; before calling, get the maximum debit from estimate_cost (free) and tell the user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>"
    },
    "name": "search_influencers"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoname or topic words to search for (creator name, channel topic)
sortNoorder: followers (default), views, videos or last_video; Instagram supports followers only
limitNomax rows (default 10, at most 10; each row with statistics costs 1 MCP credit)
nicheNoYouTube only: the directory's own niche label (exact match, comma separated), e.g. 'Mobile Games'. Unsure of the label — use q
offsetNopagination offset, a multiple of limit (0, 10, 20…)
countryNoISO-2 code (US, BR, DE…) or the English country name as the directory writes it ('United States'); comma separated for several. Matches the creator's country, not the audience's
categoryNothe directory's own category label (exact match, comma separated), e.g. Gaming or 'Beauty & Makeup'. Unsure of the label — use q
platformYesdirectory to search: youtube or instagram
has_emailNotrue = only creators with an email in the directory (the email itself is never returned)
followers_maxNomaximum subscribers (YouTube) / followers (Instagram)
followers_minNominimum subscribers (YouTube) / followers (Instagram)
last_video_daysNoonly creators active in the last N days (last video on YouTube, last post on Instagram)

Output Schema

NameRequiredDescriptionDefault
dataNo
noteNo
errorNoPresent only when isError is true: machine-readable failure. The human explanation stays in content.
offsetNo
paramsNoRequest parameter echo: applied = parameters that shaped this result; normalized = parameters rewritten before applying (alias, type coercion, resolved id); ignored = parameters that were accepted but NOT applied, with the reason.
has_moreNo
platformNo
total_noteNo
addon_hintsNoAdd-on modules that have additional data for objects of this result (no prices, no paid values). subscription_status=active: the account has the module — use its normal path. Do not push a purchase the user did not ask about.
contacts_noteNo
total_estimateNo
credits_exhaustedNo
subscription_lockedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / data / items / properties / admin_source
      Added value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"max rows (default 10, at most 10; each row with statistics costs 1 token)"New value: +"max rows (default 10, at most 10; each row with statistics costs 1 MCP credit)"
    • addedOutput schema / properties / addon_hints
      Added value: +{
      +  "description": "Add-on modules that have additional data for objects of this result (no prices, no paid values). subscription_status=active: the account has the module — use its normal path. Do not push a purchase the user did not ask about.",
      +  "items": {
      +    "properties": {
      +      "available_data_types": {
      +        "description": "kinds of data the module confirmedly has for the object",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "info_url": {
      +        "description": "the object (or its limited breakdown) inside the module on spytrend.com",
      +        "type": "string"
      +      },
      +      "module": {
      +        "description": "nutra | crypto | web2app | search_arb | startups",
      +        "type": "string"
      +      },
      +      "object_id": {
      +        "description": "the ad id, or the site domain for site rows",
      +        "type": "string"
      +      },
      +      "preland_downloadable": {
      +        "description": "Nutra / Crypto: the saved pre-lander can be downloaded in the module",
      +        "type": "boolean"
      +      },
      +      "subscription_status": {
      +        "description": "active | not_connected",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/non-destructive annotations, the description discloses substantial non-obvious behavior: contacts are never returned, total_estimate is only an estimate, limit and offset pagination constraints, subscription_locked teaser behavior, MCP credit quota, and pricing terms. These are exactly the operational details an agent needs before calling.

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?

The purpose and platform requirement are front-loaded, and most of the dense text carries necessary operational detail. It is overlong in places, especially the long YouTube category example list and the row-field enumeration that partly duplicates the output schema, but it remains usable and structured around filters, rows, and pricing.

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 12 parameters, subscription behavior, quota, and pricing complexity, the description covers what an agent must know before calling. Since an output schema exists, the description need not fully explain return values, and the extra row-field details are supplemental rather than a completeness requirement.

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 the schema already documents parameters, but the description adds meaningful semantics: YouTube category examples, exact-match comma-separated label behavior, niche/category being YouTube-only, country matching the creator rather than the audience, and Instagram sort limited to followers. These go beyond the schema and help prevent misuse.

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?

The description opens with a specific verb and resource: search the INFLUENCER directory, defined as the website's /influence page covering YouTube channels and Instagram accounts. It states the required platform and makes the scope distinguishable from other search_* tools without requiring the schema.

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

Usage Guidelines4/5

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

It gives clear usage context: platform is required, q should be used when category or niche labels are uncertain, and estimate_cost should be called before the paid search. It does not explicitly contrast this tool with the sibling get_influencer tool for retrieving a single creator, so the alternatives guidance is not fully complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.