ShortsIntel

Get a video

get_video

Use when you have one video (URL, or platform + id) and need its metadata, stats, Scores, analysis, transcript or file. Not for its comments: use get_comments. Not for an outlier verdict: use score_video. Price: 3 credits plain; include intelligence 23 credits instead; transcript only 10 credits instead; download 3 credits alone, else +3 credits. include intelligence: the full analysis (hook, CTA, tone, timed transcript, timed scenes); transcript: the speech alone; download: a file link (download_expires_at). Over 10 minutes: video_too_long; gone or private: media_unavailable; uncharged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_video"
  }
}

Input Schema

Name	Required	Description
`id`	No	The platform's own video id
`url`	No	TikTok, Instagram, YouTube or Facebook video URL. Pass this or platform + id
`include`	No
`refresh`	No	Recompute Intelligence even when a cached pass exists
`estimate`	No	Quote the price in Credits: no Run, no charge
`platform`	No
`max_credits`	No
`idempotency_key`	No	Reuse on a retry: replays the original Run, not charged again

Output Schema

Name	Required	Description
`run`	No
`cached`	No
`result`	No	One normalised video, the same shape on every platform.
`poll_url`	No
`estimate_credits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 5, 2026

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"

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"
+    },
+    "result": {
+      "$ref": "#/properties/run",
+      "description": "One normalised video, the same shape on every platform."
+    },
+    "run": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true; the description earns credit by explaining why this charged fetch is not a plain read, and by disclosing credit pricing tiers (3 / 23 / 10 credits, download add-on), enumerated failure modes (video_too_long over 10 minutes, media_unavailable for gone/private), and that failures are uncharged. It stops short of covering auth or rate limits, so it is strong rather than complete.

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?

Front-loads the use case and alternatives, then pricing, then parameter meanings, then error behavior, with no filler sentences. The style is telegraphic fragments, which costs a little readability but keeps density high and every line load-bearing.

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 an 8-parameter, zero-required tool with an output schema (so return shapes need not be described), the definition covers routing, cost, mode selection, and failure semantics. The remaining gap is that cost-control parameters like estimate and max_credits are never explained at the tool level.

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 63%, and the description compensates well on the highest-risk parameter by defining each include enum value ('intelligence: the full analysis (hook, CTA, tone, timed transcript, timed scenes)', 'transcript: the speech alone', 'download: a file link (download_expires_at)'). It adds nothing about refresh, estimate, max_credits, or idempotency_key, so half the parameters rely on the schema alone.

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 plus the exact input shapes it accepts ('one video (URL, or platform + id)') and enumerates what it returns: metadata, stats, Scores, analysis, transcript, file. It then explicitly distinguishes itself from get_comments (comments) and score_video (outlier verdict), so an agent can route without opening a 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?

Opens with the triggering condition ('when you have one video and need its metadata...') and gives two explicit exclusions naming the correct siblings for comments and for an outlier verdict. This is the when/when-not/alternatives pattern done properly.

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?