hooklayer

trend_pulse

Idempotent

Research what is currently gaining traction in short-form content for a specific niche. Returns rising opportunities (formats, hooks, styles, topics) with growth signals, data sources, and saturated patterns to avoid. Use when the user asks what to post about, what's trending in a niche, or needs to validate a content idea against current trends. Supports the 18 canonical niches and optional region filtering.

Input Schema

TableJSON Schema

Name	Required	Description
`niche`	No	One of the 18 supported niches (Beauty & Skincare, Fitness & Health, Food & Cooking, Fashion & Style, Tech & Gadgets, Finance & Business, Education & Learning, Travel & Adventure, Comedy & Entertainment, Gaming, Lifestyle & Wellness, Parenting & Family, DIY & Crafts, Music & Dance, Pets & Animals, Sports, Motivation & Self-Help, SaaS & AI Tools). Loose names like "travel" or "fitness" are accepted but pass the canonical form when possible. Omit for broadly applicable trends.
`region`	No	Optional 2-letter ISO country code (US, GB, BR, JP, IN, PH, etc.). Threads to Google Trends geo + YouTube regionCode. Defaults to US when omitted. Reddit signals are global and ignore this param.
`deadline_hours`	No	Optional (2026-07-06 magic-genie ritual): how many hours until the video posts. When set, each rising trend gets a trend_status (up-slope \| plateau \| fading \| unknown) AND a deadline_verdict (safe \| risky \| no-go) so managers can answer "will this trend still be alive when the video posts?" without eyeballing the growth label. Use this on every brief-just-landed call — it turns trend_pulse from "what's trending" into "what's SAFE to bet on for MY post window."

Output Schema

TableJSON Schema

Name	Required	Description
`niche`	No	The niche these trends apply to
`rising`	No	Rising opportunities (format/hook/style) with qualitative growth labels + signal_strength numeric anchor (0-1) + suggestions
`from_payg`	No	Whether credits came from pay-as-you-go balance
`saturated`	No	Saturated patterns to avoid
`credits_remaining`	No	Credits remaining after this call
`from_subscription`	No	Whether credits came from subscription

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

changedInput schema / properties / niche / description

Previous value: -"One of the 17 supported niches. Loose names like \"travel\" or \"fitness\" are accepted but pass the canonical form when possible. Omit for broadly applicable trends."New value: +"One of the 18 supported niches (Beauty & Skincare, Fitness & Health, Food & Cooking, Fashion & Style, Tech & Gadgets, Finance & Business, Education & Learning, Travel & Adventure, Comedy & Entertainment, Gaming, Lifestyle & Wellness, Parenting & Family, DIY & Crafts, Music & Dance, Pets & Animals, Sports, Motivation & Self-Help, SaaS & AI Tools). Loose names like \"travel\" or \"fitness\" are accepted but pass the canonical form when possible. Omit for broadly applicable trends."

Changed1 schema field changedJul 7, 2026

addedInput schema / properties / deadline_hours

Added value: +{
+  "description": "Optional (2026-07-06 magic-genie ritual): how many hours until the video posts. When set, each rising trend gets a trend_status (up-slope | plateau | fading | unknown) AND a deadline_verdict (safe | risky | no-go) so managers can answer \"will this trend still be alive when the video posts?\" without eyeballing the growth label. Use this on every brief-just-landed call — it turns trend_pulse from \"what's trending\" into \"what's SAFE to bet on for MY post window.\"",
+  "maximum": 168,
+  "minimum": 1,
+  "type": "integer"
+}

Changed1 schema field changedJun 10, 2026

changedInput schema / properties / niche / enum

Previous value: -[
-  "Beauty & Skincare",
-  "Fitness & Health",
-  "Food & Cooking",
-  "Fashion & Style",
-  "Tech & Gadgets",
-  "Finance & Business",
-  "Education & Learning",
-  "Travel & Adventure",
-  "Comedy & Entertainment",
-  "Gaming",
-  "Lifestyle & Wellness",
-  "Parenting & Family",
-  "DIY & Crafts",
-  "Music & Dance",
-  "Pets & Animals",
-  "Sports",
-  "Motivation & Self-Help"
-]New value: +[
+  "Beauty & Skincare",
+  "Fitness & Health",
+  "Food & Cooking",
+  "Fashion & Style",
+  "Tech & Gadgets",
+  "Finance & Business",
+  "Education & Learning",
+  "Travel & Adventure",
+  "Comedy & Entertainment",
+  "Gaming",
+  "Lifestyle & Wellness",
+  "Parenting & Family",
+  "DIY & Crafts",
+  "Music & Dance",
+  "Pets & Animals",
+  "Sports",
+  "Motivation & Self-Help",
+  "SaaS & AI Tools"
+]

Changed1 schema field changedJun 10, 2026

addedInput schema / properties / region

Added value: +{
+  "description": "Optional 2-letter ISO country code (US, GB, BR, JP, IN, PH, etc.). Threads to Google Trends geo + YouTube regionCode. Defaults to US when omitted. Reddit signals are global and ignore this param.",
+  "type": "string"
+}

Changed2 schema fields changedJun 3, 2026

changedOutput schema / properties / rising / description

Previous value: -"Rising opportunities (format/hook/style) with growth rates and suggestions"New value: +"Rising opportunities (format/hook/style) with qualitative growth labels + signal_strength numeric anchor (0-1) + suggestions"

addedOutput schema / properties / rising / items / properties / growth / description

Added value: +"Qualitative growth label (\"Rising\", \"Early signal\", \"Accelerating\"). NOT a numeric percentage — the upstream does not compute \"+178%\"-style rates. Use signal_strength as the quantitative anchor."

Changed2 schema fields changedMay 23, 2026

changedInput schema / properties / niche / description

Previous value: -"Niche filter (e.g. \"Beauty & Skincare\", \"Fitness & Health\"). Omit for broadly applicable trends."New value: +"One of the 17 supported niches. Loose names like \"travel\" or \"fitness\" are accepted but pass the canonical form when possible. Omit for broadly applicable trends."

addedInput schema / properties / niche / enum

Added value: +[
+  "Beauty & Skincare",
+  "Fitness & Health",
+  "Food & Cooking",
+  "Fashion & Style",
+  "Tech & Gadgets",
+  "Finance & Business",
+  "Education & Learning",
+  "Travel & Adventure",
+  "Comedy & Entertainment",
+  "Gaming",
+  "Lifestyle & Wellness",
+  "Parenting & Family",
+  "DIY & Crafts",
+  "Music & Dance",
+  "Pets & Animals",
+  "Sports",
+  "Motivation & Self-Help"
+]

Changed1 schema field changedMay 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "credits_remaining": {
+      "description": "Credits remaining after this call",
+      "type": "number"
+    },
+    "from_payg": {
+      "description": "Whether credits came from pay-as-you-go balance",
+      "type": "boolean"
+    },
+    "from_subscription": {
+      "description": "Whether credits came from subscription",
+      "type": "boolean"
+    },
+    "niche": {
+      "description": "The niche these trends apply to",
+      "type": "string"
+    },
+    "rising": {
+      "description": "Rising opportunities (format/hook/style) with growth rates and suggestions",
+      "items": {
+        "properties": {
+          "growth": {
+            "type": "string"
+          },
+          "suggestion": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "saturated": {
+      "description": "Saturated patterns to avoid",
+      "items": {
+        "properties": {
+          "status": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations supply openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the behavioral bar is lowered; the description usefully adds that results include growth signals, data sources, and saturated patterns to avoid. However it does not reconcile the tension between the read-flavored 'Research/Returns' framing and readOnlyHint=false, nor mention latency or external-source behavior for an open-world research call.

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?

Three sentences, front-loaded with purpose and then usage, with no filler and a clean reading order. It is efficiently sized for the complexity, though the niche/region sentence is largely redundant with the schema.

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?

An output schema exists, so return values need not be restated, and the description covers purpose, triggers, and scoping (niche, region). The one gap is that the significant deadline_hours parameter and its deadline_verdict behavior are neither referenced nor alluded to in the description.

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

Parameters3/5

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

Schema description coverage is 100%, so the enum niche list and region semantics are already fully documented in the schema; baseline 3 applies. The description only echoes '18 canonical niches' and 'optional region filtering' and never surfaces deadline_hours, but adds nothing beyond the structured fields.

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 description opens with a specific verb+resource ('Research what is currently gaining traction in short-form content for a specific niche') and enumerates the returned artifacts (formats, hooks, styles, topics). It is clearly distinguishable in intent from analyze_* and score_hook, but it never names a sibling or explicit boundary to disambiguate from find_viral_template/predict_virality.

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?

The 'Use when...' clause gives concrete trigger conditions: 'what to post about', 'what's trending in a niche', or validating a content idea against trends. That is clear when-to-use context, but there are no when-not conditions and no named alternative tool, so routing is left partly to inference.

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

All hooklayer tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.