Skip to main content
Glama

Show creator profile

render_creator_profile

Use this when the user wants a visual deep dive on one canonical creator ID. It fetches the current creator record plus up to six recent posts and may consume Influship account or API usage.

Input Schema

NameRequiredDescriptionDefault
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
creator_idYesCanonical Influship creator ID.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

NameRequiredDescriptionDefault
viewYes
postsYes
creatorYes
postsUnavailableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "creator_id"
      -]New value: +[
      +  "creator_id",
      +  "context",
      +  "llm_model"
      +]
  2. Changed30 schema fields changed
    • removedOutput schema / properties / creator / properties / aiSummary / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / creator / properties / aiSummary / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / creator / properties / analysisUpdatedAt / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / creator / properties / analysisUpdatedAt / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / creator / properties / audienceSummary / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / creator / properties / audienceSummary / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / creator / properties / bio / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / creator / properties / bio / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / creator / properties / profiles / items / properties / dataUpdatedAt / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / creator / properties / profiles / items / properties / dataUpdatedAt / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / creator / properties / profiles / items / properties / engagementRate / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / creator / properties / profiles / items / properties / engagementRate / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / creator / properties / profiles / items / properties / followers / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / creator / properties / profiles / items / properties / followers / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / creator / properties / vibe / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / creator / properties / vibe / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / posts / items / properties / caption / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / posts / items / properties / caption / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / posts / items / properties / comments / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / posts / items / properties / comments / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / posts / items / properties / engagementRate / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / posts / items / properties / engagementRate / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / posts / items / properties / likes / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / posts / items / properties / likes / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / posts / items / properties / postedAt / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / posts / items / properties / postedAt / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / posts / items / properties / type / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / posts / items / properties / type / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / posts / items / properties / views / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / posts / items / properties / views / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  3. Changed7 schema fields changed
    • addedOutput schema / properties / creator / properties / analysisFactCount
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / creator / properties / analysisUpdatedAt
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • removedOutput schema / properties / creator / properties / brandAlignment
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedOutput schema / properties / creator / properties / keyFacts
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / properties / creator / properties / profiles / items / properties / dataUpdatedAt
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / properties / creator / properties / profiles / items / required
      Previous value: -[
      -  "platform",
      -  "username",
      -  "url",
      -  "followers",
      -  "engagementRate",
      -  "verified"
      -]New value: +[
      +  "platform",
      +  "username",
      +  "url",
      +  "followers",
      +  "engagementRate",
      +  "verified",
      +  "dataUpdatedAt"
      +]
    • changedOutput schema / properties / creator / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "bio",
      -  "avatarUrl",
      -  "aiSummary",
      -  "audienceSummary",
      -  "brandAlignment",
      -  "contentThemes",
      -  "keyFacts",
      -  "vibe",
      -  "profiles"
      -]New value: +[
      +  "id",
      +  "name",
      +  "bio",
      +  "avatarUrl",
      +  "aiSummary",
      +  "analysisUpdatedAt",
      +  "analysisFactCount",
      +  "audienceSummary",
      +  "contentThemes",
      +  "vibe",
      +  "profiles"
      +]
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: the payload scope (current record plus up to six recent posts) and a cost warning that the call may consume Influship account or API usage, which also explains why readOnlyHint is false despite being a fetch-style operation. It does not cover rendering output characteristics or failure modes, but the quota disclosure is the non-obvious detail an agent needs.

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?

Two sentences, zero filler, with the usage trigger front-loaded and the cost caveat following. Nothing is repeated from the schema or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is unnecessary, and the description covers the data fetched and the quota cost. The remaining gap is positioning against get_creator and the other render_* siblings, which an agent must infer.

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%, including detailed guidance for context, llm_model, and conversation_id, so the schema does the heavy lifting. The description echoes 'canonical creator ID' but adds no format or constraint detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action and scope: a visual deep dive on one canonical creator ID, fetching the current creator record plus up to six recent posts. The 'visual deep dive' phrasing and 'one' creator ID indirectly separate it from render_creator_comparison and render_creator_shortlist, but no sibling is named explicitly, so the distinction from get_creator remains inferential.

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?

"Use this when the user wants a visual deep dive on one canonical creator ID" is a concrete trigger condition with an implicit scope qualifier (single creator). It gives no explicit exclusions or named alternatives such as get_creator for raw data or render_creator_comparison for multiple creators.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.