Skip to main content
Glama
Influship

Influship MCP

Official
by Influship

lookup_profiles

Read-only

Batch-fetch up to 100 social media profiles by platform and username. Ideal for comparing multiple accounts or checking if handles are real in one request.

Instructions

Batch-fetch up to 100 profiles by (platform, username) pairs.

Use this when the user has a list of handles and you need profile data for all of them at once (e.g., "give me follower counts for these 30 accounts I'm considering" or "which of @a @b @c are real accounts?"). One round-trip beats 30 calls to get_profile.

Use this for exact batch handle lookup, not semantic discovery. For one exact platform+username pair, use get_profile. For partial or fuzzy handle/name input, use search_creators or autocomplete_creators. Use semantic_search_creators only for topical/niche/audience discovery where false-positive semantic matches are acceptable.

Examples:

  • User: "Compare @a, @b, and @c on Instagram" -> use this tool for the exact handle batch.

  • User: "Give me follower counts for these 30 accounts" -> use this tool.

  • User: "Find wellness creators in Austin" -> use semantic_search_creators, not this tool.

The response splits results into data (profiles found) and not_found (the (platform, username) pairs that weren't recognized). Profiles are returned in no particular order — re-correlate via the platform/username fields if you need to preserve input order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profilesYesProfiles to lookup

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
resultsNo
countNo
okNo
not_foundNo
has_moreNo
next_cursorNo
suggested_followupsNo
Behavior5/5

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

Annotations readOnlyHint=true and destructiveHint=false indicate safe read. The description adds beyond annotations by stating response splits into data and not_found, and that profiles are returned in no particular order, requiring re-correlation for order preservation. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with purpose, then usage guidelines, examples, and behavioral notes. Every sentence adds value, no fluff. Appropriate length for the complexity.

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 tool's complexity (one complex array parameter), the description covers purpose, usage, response structure (data/not_found), and ordering behavior. It references output schema implicitly. No gaps for agent decision or invocation.

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% with descriptions for platform (enum) and username (string constraints). The description adds context about batch size limit (up to 100) but otherwise rephrases schema info. With high coverage, 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 clearly states 'Batch-fetch up to 100 profiles by (platform, username) pairs,' specifying the action, resource, and key parameters. It distinguishes from siblings like get_profile (single) and semantic_search_creators (fuzzy/topical) by emphasizing exact batch lookup.

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?

Explicit when-to-use guidance is given: 'Use this when the user has a list of handles...' and 'One round-trip beats 30 calls to get_profile.' When-not-to-use scenarios and alternatives are named: get_profile for single exact, search_creators/autocomplete_creators for fuzzy, semantic_search_creators for topical. Examples further clarify.

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/Influship/influship-mcp'

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