Skip to main content
Glama
Influship

Influship MCP

Official
by Influship

get_creator

Read-only

Retrieve a creator's full record by UUID or by platform and username. Includes optional social profile summaries.

Instructions

Fetch the full record for a single creator by ID or exact platform username.

Use this when you already have either:

  • a canonical creator UUID returned by search_creators, semantic_search_creators, autocomplete_creators, or find_lookalike_creators; or

  • an exact platform+username pair such as platform "instagram" and username "niickjackson".

Pass include: ['profiles'] to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context.

Examples:

  • User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id.

  • User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use get_profile if profile metrics are the main need.

  • User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use get_profile/get_posts for platform-specific metrics and content if needed.

Use lookup_profiles for batch exact profile lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoCreator unique identifier
platformNoSocial platform for the username.
usernameNoPlatform username or handle without the @ sign.
includeNoAdditional data to include in response

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 already indicate readOnlyHint and non-destructive. Description adds behavioral details: resolution through profile endpoint for platform+username, combined return, and include parameter effect. 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 bullet points and examples, but slightly longer than minimal. However, every sentence adds value and it's front-loaded with purpose.

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 output schema exists (not shown but noted), description doesn't need return details. It covers input modes, resolution, alternatives, and handling of include. Complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but description adds context on parameter usage, the two input modes, and the include parameter behavior. Examples clarify real-world usage.

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 the tool fetches the full record for a single creator by ID or exact platform+username. It distinguishes from siblings like search_creators, get_profile, and lookup_profiles via examples.

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?

Explicitly states when to use (have UUID or exact platform+username) and when not to use (batch lookups -> lookup_profiles; profile metrics -> get_profile). Provides clear alternatives.

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