Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Find creators on YouTube, Instagram, TikTok and Vimeo

find_creators
Read-onlyIdempotent

Search YouTube, Instagram, TikTok and Vimeo creators by keyword or profile link and retrieve follower, engagement, contact and lead-score data for influencer outreach.

Instructions

Creators from YouTube and Vimeo search words, or YouTube, Instagram, TikTok and Vimeo profile links: followers, video count, average views, likes and comments over the latest posts, engagement rate, last post date, country, bio, website, other social accounts, public emails and a lead score. No login. Useful for influencer marketing, sponsorship outreach and creator research. Runs the Apify Actor tacps126/creator-finder on your Apify account (about $0.002 per creator, $0.001 per video or post; spend per call is capped at $0.5).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksNoYouTube, Instagram, TikTok or Vimeo profile or video links.
queriesNoSearch words for YouTube and Vimeo, e.g. ["home barista"].
max_itemsNoMaximum results to return (default 50, max 1000). Cost scales with this.
platformsNoWhere to search (default both).
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
max_followersNoMost followers or subscribers.
min_followersNoFewest followers or subscribers.
posts_per_creatorNoLatest videos or posts to add per creator (also used for averages).
min_engagement_rateNoLowest engagement rate in percent, e.g. 2.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the description's job is lighter and it adds real value: no login required, it runs the Apify Actor tacps126/creator-finder on the caller's own Apify account, unit pricing (~$0.002/creator, $0.001/video or post) and a $0.5 per-call spend cap. Latency and failure behavior are unstated, keeping it below a 5.

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 resource and accepted inputs, then outputs, then cost — a sensible order. The middle output enumeration is long but each item is a real returned field an agent would want to know about; the only friction is the slightly tangled opening clause.

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?

For a nine-parameter, nested-input, open-world scraping tool with a full output schema and complete annotations, the description covers inputs, cost implications and the no-auth requirement. Only runtime behavior and cost interaction with posts_per_creator (beyond the schema note) are left implicit.

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 description coverage is 100%, so all nine parameters (including max_items, posts_per_creator and the follower bounds) are already documented. The description adds only the either/or framing between search words and profile links; it gives no extra meaning for the advanced extra_input merge field or the engagement filter.

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+resource (find creators) and precisely scopes the accepted inputs: search words for YouTube/Vimeo and profile/video links for YouTube, Instagram, TikTok and Vimeo. The enumerated output fields (followers, engagement rate, emails, lead score) make it instantly distinguishable from siblings like get_instagram_posts or get_youtube_transcripts.

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?

"Useful for influencer marketing, sponsorship outreach and creator research" gives clear use context, and the input-mode framing implies when to use queries vs links. It stops short of naming alternatives or stating when another sibling tool would be the better pick, so it does not reach a 5.

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