Skip to main content
Glama

Influship

by io.github.Influship

Get sample creator

get_sample_creator
Read-only

Use this when a user wants to see what Influship can return before linking an account.

Fetches one configured sample creator with social profile context. This is a preview tool and should not be used for search, discovery, matching, or comparison requests. After showing the preview, explain only that live creator discovery and comparison require connecting an existing Influship account. Do not discuss plans, pricing, credits, upgrades, or purchasing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewYes
postsYes
creatorYes
postsUnavailableYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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"
+]
  2. Changed14 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +false
    • removedOutput schema / properties / count
      Removed value: -{
-  "type": "number"
-}
    • addedOutput schema / properties / creator
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "aiSummary": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "audienceSummary": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "avatarUrl": {
+      "anyOf": [
+        {
+          "format": "uri",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "bio": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "brandAlignment": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "contentThemes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "id": {
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    "keyFacts": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": "string"
+    },
+    "profiles": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "engagementRate": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "followers": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "platform": {
+            "type": "string"
+          },
+          "url": {
+            "anyOf": [
+              {
+                "format": "uri",
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "username": {
+            "type": "string"
+          },
+          "verified": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "platform",
+          "username",
+          "url",
+          "followers",
+          "engagementRate",
+          "verified"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "vibe": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "bio",
+    "avatarUrl",
+    "aiSummary",
+    "audienceSummary",
+    "brandAlignment",
+    "contentThemes",
+    "keyFacts",
+    "vibe",
+    "profiles"
+  ],
+  "type": "object"
+}
    • removedOutput schema / properties / data
      Removed value: -{}
    • removedOutput schema / properties / has_more
      Removed value: -{
-  "type": "boolean"
-}
    • removedOutput schema / properties / next_cursor
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}
    • removedOutput schema / properties / not_found
      Removed value: -{
-  "items": {},
-  "type": "array"
-}
    • removedOutput schema / properties / ok
      Removed value: -{
-  "type": "boolean"
-}
    • addedOutput schema / properties / posts
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "caption": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "comments": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "engagementRate": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "type": "string"
+      },
+      "likes": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "platform": {
+        "type": "string"
+      },
+      "postedAt": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "thumbnailUrl": {
+        "anyOf": [
+          {
+            "format": "uri",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "type": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "url": {
+        "anyOf": [
+          {
+            "format": "uri",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "views": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "platform",
+      "url",
+      "postedAt",
+      "type",
+      "caption",
+      "thumbnailUrl",
+      "likes",
+      "comments",
+      "views",
+      "engagementRate"
+    ],
+    "type": "object"
+  },
+  "maxItems": 6,
+  "type": "array"
+}
    • addedOutput schema / properties / postsUnavailable
      Added value: +{
+  "type": "boolean"
+}
    • removedOutput schema / properties / results
      Removed value: -{
-  "items": {},
-  "type": "array"
-}
    • removedOutput schema / properties / suggested_followups
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "reason": {
-        "type": "string"
-      },
-      "tool": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "tool",
-      "reason"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / view
      Added value: +{
+  "const": "profile",
+  "type": "string"
+}
    • addedOutput schema / required
      Added value: +[
+  "view",
+  "creator",
+  "posts",
+  "postsUnavailable"
+]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds valuable behavioral context by clarifying it returns one configured sample creator with social profile context, framing it as a preview, and instructing the agent on what to say after showing the preview. This exceeds what annotations alone provide.

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 concise and front-loaded with the primary use case. Every sentence earns its place: the first states when to use it, the second defines the tool's behavior and exclusions, and the third gives necessary post-invocation guidance. No redundant or promotional language is present.

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 tool's low complexity, zero parameters, existing output schema, and read-only annotations, the description covers everything needed to invoke and respond correctly. It includes when to use the tool, what it does, what it should not be used for, and even the required follow-up message.

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?

The input schema has zero parameters, so there is no parameter semantics for the description to add. With schema coverage at 100%, the baseline of 4 applies; the description does not need to compensate for missing parameter documentation.

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 states a specific verb and resource: 'Fetches one configured sample creator with social profile context.' It clearly identifies this as a preview tool and distinguishes it from search, discovery, matching, and comparison requests, making it easy to separate from siblings like search_creators and match_creators.

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?

Usage context is explicit: use when a user wants to preview what Influship can return before linking an account. It also explicitly states what not to use it for and provides post-preview conversational instructions, leaving no ambiguity about when or how to apply this tool.

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

All Influship toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Multiple tools have unclear boundaries: `autocomplete_creators` and `search_creators` both claim the exact same example query ('Who is that fitness coach called Jane?') as their primary use case, creating direct routing conflicts. `get_creator` and `get_profile` also overlap heavily for exact platform+username lookups, with descriptions admitting the choice depends on whether 'profile metrics are the main need' — a thin distinction. `search_creators` further muddies things by dual-routing to legacy semantic search, making it a hybrid that competes with both `autocomplete_creators` and `semantic_search_creators`.

Naming Consistency4/5

The naming follows a mostly consistent verb_noun snake_case pattern: `get_*` covers record fetching, with clear singular/batch pairs like `get_instagram_post`/`get_instagram_posts` and transcript variants. Minor deviations exist (`semantic_search_creators` prefixes a modifier, and `autocomplete_`, `find_`, `match_`, `lookup_`, `render_` each introduce different verbs), but the style is uniform and the verb typically reflects the operation type.

Tool Count3/5

At 28 tools the server is heavy, but the scope is genuinely broad — three platform-specific data surfaces (Instagram, TikTok, YouTube), each requiring profile/video/transcript/listing operations, plus creator search, matching, and rendering. The count is inflated by redundancy, though: four `render_*` tools that could collapse into one parameterized tool, and batch variants of the Instagram raw-data endpoints. It is borderline acceptable for the platform-multiplied domain rather than chaotic bloat.

Completeness4/5

The tool surface covers the full read-only creator workflow: fuzzy lookup (autocomplete/search), exact profile fetch (get_profile/lookup_profiles), discovery (semantic_search/find_lookalike), fit scoring (match_creators), content evidence (get_posts), and presentation (render_*). Notable gaps include no Instagram-specific profile endpoint (odd given TikTok/YouTube have dedicated ones), no YouTube comments, and no audience-demographic data, but agents can complete realistic workflows without dead ends.

Resources