Skip to main content
Glama

Get a public creator

get_creator
Read-only

Get a public/competitor creator's profile by platform + handle (e.g. instagram, 'natgeo').

Only returns creators already in the analysis library; it does not ingest. For a creator you haven't pulled in yet this returns reason="creator_not_in_library" (not an error) with a next_step of analyze_creator(platform, username) — call that (needs the content:ingest scope), wait for it to finish, then retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesTarget platform — instagram, tiktok, or youtube (case-insensitive).
usernameYesThe creator's public handle, e.g. 'natgeo' (no leading @).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "description": "A public/competitor creator's profile (analysis:read:public).",
      +    "properties": {
      +      "account_type": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Account Type"
      +      },
      +      "bio": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Bio"
      +      },
      +      "content_dna": {
      +        "anyOf": [
      +          {
      +            "additionalProperties": true,
      +            "type": "object"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Content Dna"
      +      },
      +      "creator_id": {
      +        "title": "Creator Id",
      +        "type": "string"
      +      },
      +      "display_name": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Display Name"
      +      },
      +      "follower_count": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Follower Count"
      +      },
      +      "following_count": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Following Count"
      +      },
      +      "platform": {
      +        "title": "Platform",
      +        "type": "string"
      +      },
      +      "profile_picture_url": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Profile Picture Url"
      +      },
      +      "username": {
      +        "title": "Username",
      +        "type": "string"
      +      },
      +      "videos_analyzed_count": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Videos Analyzed Count"
      +      }
      +    },
      +    "required": [
      +      "creator_id",
      +      "platform",
      +      "username"
      +    ],
      +    "title": "McpCreatorProfile",
      +    "type": "object"
      +  },
      +  {
      +    "description": "Soft, non-error output of `get_creator` when the creator isn't in the\nanalysis library yet. Discriminator vs. the profile variant\n(`McpCreatorProfile`): `reason` == 'creator_not_in_library'. Recover by\ncalling the tool named in `next_step`.",
      +    "properties": {
      +      "hint": {
      +        "title": "Hint",
      +        "type": "string"
      +      },
      +      "next_step": {
      +        "const": "analyze_creator",
      +        "description": "The tool to call to ingest this creator.",
      +        "title": "Next Step",
      +        "type": "string"
      +      },
      +      "platform": {
      +        "title": "Platform",
      +        "type": "string"
      +      },
      +      "reason": {
      +        "const": "creator_not_in_library",
      +        "title": "Reason",
      +        "type": "string"
      +      },
      +      "username": {
      +        "title": "Username",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "reason",
      +      "platform",
      +      "username",
      +      "next_step",
      +      "hint"
      +    ],
      +    "title": "McpCreatorNotInLibrary",
      +    "type": "object"
      +  }
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / platform / description
      Added value: +"Target platform — instagram, tiktok, or youtube (case-insensitive)."
    • addedInput schema / properties / username / description
      Added value: +"The creator's public handle, e.g. 'natgeo' (no leading @)."
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true (safe read) and openWorldHint=true (unexpected results possible). The description adds behavioral details: the tool returns a specific reason when a creator is not in the library, and it does not perform ingestion. No contradiction with annotations.

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 a single efficient paragraph with two sentences. It front-loads the core purpose and immediately adds actionable usage guidance. No unnecessary words.

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 that an output schema exists (so return values need not be described), the description covers all essential aspects: what the tool does, how to use it, edge cases (not in library), and next steps. It is fully complete for a simple lookup 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 covers 100% of parameters with descriptions. The description adds value by explaining how to use the parameters together ('platform + handle'), providing an example ('instagram, 'natgeo''), and clarifying that the username should not include a leading '@'.

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 verb ('Get'), the resource ('public/competitor creator's profile'), and the required inputs ('platform + handle') with an example. It distinguishes itself from sibling tools like analyze_creator and search by specifying that it only retrieves existing library entries.

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?

The description explicitly tells when to use the tool (for creators already in the library) and what to do if the creator is not found: it returns a specific reason and suggests calling analyze_creator. It also notes that this tool does not ingest, providing clear alternatives.

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.