ShortsIntel

Get a keyword

get_keyword

Use when you need one search phrase's sample stats, trend since the last lookup and top 10 videos by views, on one platform (tiktok, instagram, youtube or facebook). Not for results across platforms: use search_videos. Not for an analysed niche answer: use research. To watch daily: track kind=keyword. Price: 3 credits; focus +3 credits per video judged, +1 credit per must_mention rejection. One page of the platform's search (relevance, past month): a sample, not platform totals; a lookup under 24 h old answers at the same price. focus hides off-focus top videos; stats stay unfiltered.

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>",
      "phrase": "<phrase>"
    },
    "name": "get_keyword"
  }
}

Input Schema

Name	Required	Description
`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).
`phrase`	Yes	The search phrase, at most 100 characters; case and extra spaces are ignored
`estimate`	No	Quote the price in Credits: no Run, no charge
`platform`	Yes
`max_credits`	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.6/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses the credit price structure including per-video judging and must_mention rejection costs, the 24-hour cache/replay pricing rule, and the crucial caveat that results are one page of relevance-ranked search results from the past month, not platform totals. It stops short of describing what a Run is or how to retrieve async results, which the get_run sibling implies is needed.

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, then alternatives, then cost, then the sampling caveat — a sensible order. The telegraphic 'Price: 3 credits; focus +3 credits per video judged...' sentence is dense and would read faster as prose, but every sentence carries information.

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?

For a paid, open-world, non-idempotent search tool with an output schema, the description covers the things the schema cannot: cost, caching, sample-vs-totals expectations, and the filtered/unfiltered distinction. Return values are correctly left to the output schema.

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 71%, so the schema carries most parameter meaning, but the description adds genuine semantics: focus hides off-focus top videos while stats stay unfiltered, and focus/must_mention have direct credit cost implications (+3 per video judged, +1 per must_mention rejection). estimate and max_credits behaviour is only hinted at through the pricing sentence rather than explained.

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 resource and exactly what it returns: one search phrase's sample stats, trend since the last lookup, and top 10 videos by views, on one named platform. It also names the siblings it is not (search_videos, research, track), so an agent can separate it from near neighbours 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 search phrase's sample stats... on one platform') plus explicit when-not clauses with the correct alternative for each: cross-platform results go to search_videos, an analysed niche answer goes to research, and recurring monitoring goes to track kind=keyword. Nothing is left to inference.

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?