Skip to main content
Glama
Sign In
Clipwright

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Find trending reels on a topic

find_trends
Idempotent

Find short-form videos that gained traction on a topic across TikTok and Instagram, ranked by median engagement, to support UGC ad research and content planning.

Instructions

Input: the same fields as quote_trends, plus sort. Reels that took off on a topic: up to 10 per platform, one per creator, TikTok and Instagram ranked by x_median. Charged only on success, a one-platform mix too; 10 per hour. poll repeats this call; sort reorders it free. Price: 20 credits per call. Quote first with quote_trends.

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": {
      "keywords": "<keywords>"
    },
    "name": "find_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
keywordsYes
languageNo
platformNo
posted_within_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.45.0

TDQS

A3.8/5.0
Behavior5/5

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

With annotations covering only the safety profile, the description carries real behavioral weight: billing is 'charged only on success' at 20 credits, the quota is 10/hour, results are capped at 10 per platform and one per creator, ranking is by x_median, and sort is free while poll is a repeat. Those are exactly the operational facts an agent needs before spending credits and are not inferable from idempotentHint/destructiveHint.

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?

Six tight fragments, no filler, and the cost and quota land early enough to gate the call. The telegraphic style costs some readability — 'a one-platform mix too' and 'Input: the same fields as quote_trends' are compressed to the point of ambiguity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, credit-charging tool with no output schema, the description does cover result shape, ranking, pricing, rate limit, and idempotent re-runs. The remaining hole is the input contract: four of five parameters are undocumented anywhere, and the cross-reference to quote_trends assumes shared context that may not hold.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all five parameters, so the description must compensate and largely does not. Only 'sort' gets any treatment ('sort reorders it free'), while keywords, language, platform, and posted_within_days are never explained, and 'the same fields as quote_trends' pushes the burden onto a sibling the agent may not have loaded.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'Reels that took off on a topic' plus the TikTok/Instagram ranking detail identifies the resource and the result shape, which is more than the title alone conveys. It is distinguishable from quote_trends because the description positions that sibling as the pre-flight price check rather than the fetch, though the verb 'find' never appears in the body text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Quote first with quote_trends' is an explicit prerequisite that tells the agent the ordering of the two calls, and 'poll repeats this call; sort reorders it free' clarifies that re-running with a different sort is not a new workload. What is missing is a stated condition for choosing this over a general search or analysis sibling when the user has not asked for trends.

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

Deploy Server

Other Tools