Skip to main content
Glama
Influship

Influship MCP

Official
by Influship

get_profile

Read-only

Retrieve a social profile's bio, follower/engagement metrics, growth, and recent activity by platform and username for influencer analysis.

Instructions

Fetch a single social profile by (platform, username).

Always use this first when the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram") and you need the full profile: bio, follower/engagement metrics, recent activity, growth, and the canonical creator ID. Pass exactly the username they typed without the @ sign — case-insensitive matching is handled server-side. Do not use search_creators for an exact platform+username lookup.

Examples:

  • User: "Pull @niickjackson on Instagram" -> use this tool with platform "instagram" and username "niickjackson".

  • User: "Tell me about instagram.com/niickjackson" -> parse the platform and username, then use this tool.

  • User: "Is @niickjackson a fit for Pixel?" -> use this tool first, then call get_posts and/or match_creators if the task needs content or fit analysis.

Returns the profile record plus the underlying creator record. If you already have a creator UUID, use get_creator instead. For batch lookups by handle, use lookup_profiles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesSocial platform for the username.
usernameYesPlatform username or handle without the @ sign.

Output Schema

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds that it returns both profile and creator record, that case-insensitivity is handled server-side, and implicitly confirms read-only behavior. No contradictions.

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?

Well-structured with bolded purpose, bullet-point examples, and clear usage notes. Slightly verbose but front-loaded with the critical information, every sentence is relevant.

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 presence of an output schema, the description effectively covers context: when to use, alternatives, parameter format, and error-prevention tips. No gaps for a simple 2-param tool.

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?

Input schema already covers 100% of parameters with descriptions. The description adds value by advising to omit the '@' sign and providing examples of how to parse platform and username from user input.

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 explicitly states 'Fetch a single social profile by (platform, username)' and lists the returned data (bio, metrics, growth, etc.), clearly distinguishing it from siblings like search_creators and get_creator.

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?

Provides explicit guidance: use this tool for exact handle+platform, avoid search_creators for exact lookups, and consider get_creator or lookup_profiles as alternatives. Includes concrete examples for different user inputs.

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