Skip to main content
Glama
socialintel

Social Intel MCP

search_leads

Find Instagram influencers by keyword, location, demographics, or follower range. Returns username, bio, category, and business email for about 50% of accounts. Pay per search with USDC or try free demo for up to 3 results.

Instructions

Search Instagram influencers by demographics, location, or keyword.

Returns username, bio, follower count, category, and business email (~50% of accounts).

Price: $0.50 USDC on Base or Solana via x402 (auto-handled by AgentCash or x402 client). Set demo=True to try for free — returns up to 3 results, no payment required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoKeyword or phrase to search by name/bio (e.g. 'yoga', 'travel blogger', 'NYC chef').
countryNoCountry filter. ISO code (US, DE, FR, UK, CA, AU, IN, BR, JP) or full name. Default: all countries.
cityNoCity filter (e.g. 'Los Angeles', 'London', 'New York'). Use with country for precise local targeting.
categoryNoInstagram business category. Examples: Fitness, Beauty, Travel, Food & Beverage, Gaming, Fashion, Lifestyle, Sports.
genderNoGender filter: 'male' or 'female' (also accepts 'man'/'woman').
min_followersNoMinimum follower count. Use 10000 for micro-influencers, 100000 for macro-influencers.
max_followersNoMaximum follower count. Use 100000 to exclude celebrities and large brands.
limitNoResults to return (1-100, default 20). Pricing: 1-20=$0.50, 50=$0.80, 100=$1.30.
demoNoTrue = free preview (3 results, no payment). False = full paid search via x402.
Behavior5/5

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

The description covers pricing ($0.50 USDC on Base or Solana via x402), demo mode limitations (3 results, free), and notes that ~50% of accounts have a business email. This goes beyond what annotations would typically provide.

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 description is compact and front-loaded with purpose and return fields. Pricing details are valuable but could be slightly more concise. Overall efficient.

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 9 parameters with full schema documentation and no output schema, the description covers pricing, demo mode, and email availability. This is sufficient for an agent to use the tool correctly.

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 the description adds limited meaning beyond schema. It only mentions query, country, city, etc., but the schema already documents parameters well. 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?

The description states the tool searches Instagram influencers by demographics, location, or keyword, and specifies what it returns (username, bio, follower count, category, business email). This clearly defines the action and output, distinguishing it from potential siblings.

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?

The description explains when to use demo mode vs paid mode, but does not provide direct alternatives or when-not-to-use scenarios. Since there are no sibling tools, this is acceptable.

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/socialintel/socialintel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server