Influship MCP

Official

by Influship

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

get_creator

Read-only

Fetch a complete creator record using a UUID or exact platform username. Optionally include 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

Name	Required	Description
`id`	No	Creator unique identifier
`include`	No	Additional data to include in response
`platform`	No	Social platform for the username.
`username`	No	Platform username or handle without the @ sign.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`data`	No
`count`	No
`results`	No
`has_more`	No
`not_found`	No
`next_cursor`	No
`suggested_followups`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. Description adds context about resolution behavior for platform+username inputs and the effect of the include parameter. 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. Slightly long but every sentence adds value; examples are instructive.

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 and annotations, the description is comprehensive: covers purpose, usage, parameters, examples, and tool differentiation. No gaps.

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?

Schema coverage is 100% so baseline is 3. Description adds value by explaining the two usage modes, providing examples, and clarifying the include parameter's behavior in both modes.

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?

Clearly states 'Fetch the full record for a single creator by ID or exact platform username.' Distinguishes two input modes and contrasts with sibling tools like search_creators and get_profile.

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 says when to use ('when you already have a canonical creator UUID or exact platform+username pair') and when to use alternatives (get_profile for profile metrics, lookup_profiles for batch lookups).

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

Deploy Server