ShortsIntel

Search videos

search_videos

Use when you need a page of videos matching a query across TikTok, Instagram and YouTube (Facebook opt-in). Not for a ranked, analysed niche answer: use research. Not for one phrase's stats and trend on one platform: use get_keyword. Price: 3 credits per platform per page (9 credits for the default three); +20 credits per video analysed with intelligence=true (top 20); focus +3 credits per video judged, +1 credit per must_mention rejection. Up to 30 a page (default 25); next_cursor pages. Instagram and Facebook are best-effort. Videos over 10 minutes are not analysed.

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": {
      "query": "<query>"
    },
    "name": "search_videos"
  }
}

Input Schema

Name	Required	Description
`sort`	No
`focus`	No	Which Videos are relevant to you, in plain language with any exclusions, e.g. 'Apple Inc. and its products. Not the fruit or recipes.' Off-focus Videos are hidden and counted in off_focus_count; unjudged_count counts shown Videos not judged. Optional must_mention terms cheaply rule out a Video whose captions or transcript name none (one with neither goes to the model).
`limit`	No
`query`	Yes
`cursor`	No
`region`	No
`window`	No
`estimate`	No	Quote the price in Credits: no Run, no charge
`platforms`	No
`max_credits`	No
`intelligence`	No
`idempotency_key`	No	Reuse on a retry: replays the original Run, not charged again
`include_off_focus`	No	With focus: true returns every Video with its focus verdict and reason, off-focus ones included.

Output Schema

Name	Required	Description	Default
`run`	No
`cached`	No
`result`	No
`poll_url`	No
`estimate_credits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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 / focus / description

Previous value: -"Which Videos are relevant to you, in plain language with any exclusions, e.g. 'Apple Inc. and its products (iPhone, Mac, AirPods). Not the fruit, recipes or orchards.' Off-focus Videos are hidden and counted in off_focus_count; unjudged_count counts shown Videos that could not be judged. Optional must_mention terms rule out cheaply a Video whose captions or transcript name none of them (one with neither goes to the model)."New value: +"Which Videos are relevant to you, in plain language with any exclusions, e.g. 'Apple Inc. and its products. Not the fruit or recipes.' Off-focus Videos are hidden and counted in off_focus_count; unjudged_count counts shown Videos not judged. Optional must_mention terms cheaply rule out a Video whose captions or transcript name none (one with neither goes to the model)."

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"
+    },
+    "run": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare readOnly=false, openWorld=true, idempotent=false and destructive=false; the description adds the entire cost model (3 credits per platform per page, +20 per analysed video with intelligence, focus judging fees), pagination behaviour, and the per-platform reliability and duration limits. That is substantial value beyond the structured safety flags.

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-loaded with the use case and the two exclusions, then cost, then operational limits — a sensible ordering with no filler sentences. The pricing sentence is a dense run-on of credit figures that would read better as a short list, but every clause carries decision-relevant information.

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 13-parameter, nested-object tool with an output schema (so return values need no explanation), the definition covers the decision-critical behaviour: cost, paging, platform defaults and analysis caps. Completeness is only slightly short because the filtering parameters (region, window, sort, max_credits) have no explanation anywhere.

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 description coverage is low at 31% across 13 parameters, so the description must compensate, and it does for the cost-driving ones: platforms (default three), limit (max 30, default 25), cursor (next_cursor paging), intelligence (top 20 analysed), and focus (per-video judging and must_mention rejection costs). It leaves sort, region, window and max_credits entirely unexplained in both schema and prose, which is a real remaining 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?

Opens with a specific verb+resource+scope: a page of videos matching a query across TikTok, Instagram and YouTube, with Facebook opt-in. It immediately separates itself from sibling tools by naming 'research' and 'get_keyword' as different jobs, 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 negative routing: not for a ranked, analysed niche answer (use research) and not for one phrase's stats/trend on one platform (use get_keyword). It also states operational caveats that affect the decision to call it, such as Instagram/Facebook being best-effort and videos over 10 minutes not being analysed.

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?