ShortsIntel

Get a creator

get_creator

Use when you need one creator's profile: followers, published contact, baseline (median views, engagement, cadence) and Scores; include: ['videos'] adds recent videos. Not for watching them over time: use track. Not for one of their videos: use get_video or score_video. Price: 6 credits; videos pages 3 credits; intelligence=true: free page, +20 credits per analysed video (top 20). contact is what the account publishes; follow anti-spam law when using it. next_cursor pages videos. intelligence: true analyses its stored videos (fetch include: ['videos'] first).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>",
      "handle": "<handle>"
    },
    "name": "get_creator"
  }
}

Input Schema

Name	Required	Description
`limit`	No	With intelligence: true, videos on the page (default 25).
`cursor`	No	next_cursor of a previous get_creator on this creator, for its next page of videos: from an include: ['videos'] call, or with intelligence: true from an intelligence: true call.
`handle`	Yes	@handle or plain handle; on YouTube also a channel id (UC…)
`include`	No
`estimate`	No	Quote the price in Credits: no Run, no charge
`platform`	Yes
`max_credits`	No
`videos_from`	No	Instagram (and Facebook) only: the feed include: ['videos'] reads, reels (default) or posts (carousels included).
`intelligence`	No	Analyse the creator's stored videos instead of a lookup: a page of those already fetched (call with include: ['videos'] first), the first 20 analysed as by search_videos.
`idempotency_key`	No	Reuse on a retry: replays the original Run, not charged again

Output Schema

Name	Required	Description
`run`	No
`items`	No
`cached`	No
`result`	No
`poll_url`	No
`next_cursor`	No	Pass back as `cursor`.
`estimate_credits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 5, 2026

changedInput schema / properties / cursor / description

Previous value: -"next_cursor from a previous get_creator for the same creator, for the next page of their videos: from one with include: ['videos'], or with intelligence: true from one with intelligence: true."New value: +"next_cursor of a previous get_creator on this creator, for its next page of videos: from an include: ['videos'] call, or with intelligence: true from an intelligence: true call."

changedInput schema / properties / estimate / description

Previous value: -"Return the price, in Credits, without running the operation or creating a Run"New value: +"Quote the price in Credits: no Run, no charge"

changedInput schema / properties / idempotency_key / description

Previous value: -"Reuse the same key when retrying: a repeat returns the original Run and is not charged again"New value: +"Reuse on a retry: replays the original Run, not charged again"

changedInput schema / properties / intelligence / description

Previous value: -"Analyse the creator's stored videos instead of looking the creator up: a page of the videos already fetched (call with include: ['videos'] first), the first 20 analysed like search_videos with intelligence."New value: +"Analyse the creator's stored videos instead of a lookup: a page of those already fetched (call with include: ['videos'] first), the first 20 analysed as by search_videos."

changedOutput schema / properties / run / additionalProperties
```
Previous value: -trueNew value: +{}
```
removedOutput schema / properties / run / properties
```
Removed value: -{}
```

Changed1 schema field changedNov 4, 2026
- addedInput schema / properties / max_credits
```
Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}
```
Changed1 schema field changedNov 4, 2026
- addedOutput schema / properties / poll_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```

Changed1 schema field changedNov 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "cached": {
+      "type": "boolean"
+    },
+    "estimate_credits": {
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "$ref": "#/properties/run"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Pass back as `cursor`.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "result": {
+      "$ref": "#/properties/run"
+    },
+    "run": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing the credit cost model per mode, the free estimate path, the fact that contact data is publisher-supplied with an anti-spam legal caution, and that next_cursor pages videos. These are billing and compliance facts an agent cannot infer from structured fields.

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?

Front-loaded with the use case, then explicitly negative routing, then cost, then caveats. The telegraphic style is dense but every clause carries information an agent needs; there is only mild restatement of the intelligence prerequisite between the cost line and the closing line.

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?

For a 10-parameter, credit-charging tool with an output schema, it covers purpose, alternatives, cost, prerequisites, pagination, and legal caution. What it omits is the meaning of max_credits (a spending guardrail) and any note on auth or rate limits.

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 70%, and the description adds real meaning on top: include: ['videos'] behavior, the cursor's paging scope, and intelligence mode's cost and ordering. It leaves max_credits and estimate functionally unexplained (max_credits has no schema description either), so it does not fully close the gap.

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?

States a specific verb and resource (fetch one creator's profile) and enumerates the payload: followers, published contact, baseline medians, Scores, plus optional videos. It explicitly distinguishes itself from siblings track, get_video, and score_video, so an agent can route without opening any schema.

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?

Gives explicit when-to-use (need one creator's profile) and two when-not-to-use cases with the correct alternative named for each (track for longitudinal, get_video/score_video for a single video). It also states a prerequisite ordering for intelligence mode: fetch include: ['videos'] first.

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

All ShortsIntel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?