Santiment

Combined Trends

combined_trends_tool

Read-only

Combined trends tool that fetches trending words, stories, and documents in parallel.

This tool provides a unified view of all trending data - words with their documents and stories - in a single response across all crypto projects.

When to use vs `trending_stories_tool`

This is a superset of trending_stories_tool: same stories, plus trending words, their context and AI-generated bull/bear summaries. It calls an LLM, so it is slower and has a tighter per-tool rate-limit sub-cap than every other tool. If only trending stories are needed, call trending_stories_tool instead; set include_words: false / include_stories: false to drop a half that is not needed. Do not call both tools for the same question.

Parameters

time_period - Time period for trending data (e.g., '1h', '6h', '1d', '7d'). Defaults to '1h' (last hour).
size - Number of items per category to return (max 10). Defaults to 10.

Only the 2 most recent trend periods are returned, whatever time_period is. A period is 1 hour for time_period up to 1d, 6 hours up to 7d, and 1 day beyond that, so e.g. '2d' returns only the last 12 hours. When older periods are dropped, metadata.notice says so and metadata.returned_since gives the start of the oldest period returned.

include_stories - Include trending stories in response. Defaults to true.
include_words - Include trending words in response. Defaults to true.

Response

trends - Combined trending data containing stories and words.
metadata - Request metadata including time period, size, and included data types.
errors - Any non-fatal errors encountered during data fetching.

Stories

title - Title of the trending story.
summary - Summary of the story.
score - Trending score.
query - Search query used to find the story.
related_tokens - List of related crypto tokens (format: "BTC_bitcoin").
bullish_sentiment_ratio - Bullish sentiment ratio.
bearish_sentiment_ratio - Bearish sentiment ratio.

Words

word - The trending word.
score - Trending score.
slug - Associated project slug (if word is project-related).
summary - AI-generated summary of discussions.
bullish_summary - Summary of bullish sentiment.
bearish_summary - Summary of bearish sentiment.
positive_sentiment_ratio - Positive sentiment ratio.
negative_sentiment_ratio - Negative sentiment ratio.
neutral_sentiment_ratio - Neutral sentiment ratio.
positive_bb_sentiment_ratio - Positive bull/bear sentiment ratio.
negative_bb_sentiment_ratio - Negative bull/bear sentiment ratio.
neutral_bb_sentiment_ratio - Neutral bull/bear sentiment ratio.
context - Related words that appear with this trending word.
documents_summary - AI-generated summary of related social media discussions.

Input Schema

TableJSON Schema

Name	Required	Description
`size`	No	Number of items per category to return (max 10). Defaults to 10.
`time_period`	No	Time period for trending data (e.g., '1h', '6h', '1d', '7d'). This parameter defines how far back to look for trending data. Only the 2 most recent trend periods are returned (1h periods up to '1d', 6h periods up to '7d', 1d periods beyond). Defaults to '1h' (last hour).
`include_words`	No	Include trending words in the response. Defaults to true.
`include_stories`	No	Include trending stories in the response. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

changedInput schema / properties / size / description

Previous value: -"Number of items per category to return (max 30).\n\nDefaults to 10.\n"New value: +"Number of items per category to return (max 10).\n\nDefaults to 10.\n"

changedInput schema / properties / time_period / description

Previous value: -"Time period for trending data (e.g., '1h', '6h', '1d', '7d').\nThis parameter defines how far back to look for trending data.\n\nDefaults to '1h' (last hour).\n"New value: +"Time period for trending data (e.g., '1h', '6h', '1d', '7d').\nThis parameter defines how far back to look for trending data.\nOnly the 2 most recent trend periods are returned\n(1h periods up to '1d', 6h periods up to '7d', 1d periods beyond).\n\nDefaults to '1h' (last hour).\n"

First observedAug 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The annotations already declare the safe-read profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely new behavioral facts: it calls an LLM, so it is slower and carries a tighter per-tool rate-limit sub-cap than every other tool. It also discloses the truncation behavior (only the 2 most recent trend periods are returned regardless of `time_period`) and the `metadata.notice` / `metadata.returned_since` signals that accompany dropped periods.

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?

The description is well front-loaded: purpose first, then the when-to-use routing, then parameters and response shape under clear headers. It is long but most of the length earns its place because there is no output schema. The 'Parameters' section duplicates schema text verbatim, a minor waste.

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?

There is no output schema, so the description correctly carries the burden of describing the return shape, and it does so thoroughly with `trends`, `metadata`, and `errors` plus the full field breakdown for Stories and Words. Combined with the routing guidance and rate-limit caveat, an agent has everything needed to call and interpret this tool.

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?

With schema description coverage at 100%, the baseline is 3, and the schema already documents all four parameters. The description adds real semantic value by explaining the period-truncation rule ('1h' periods up to 1d, 6h up to 7d, 1d beyond, so '2d' returns only the last 12 hours), which the schema states only partially. The separate 'Parameters' list, however, largely restates the schema.

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?

The description states a specific verb and resource ('fetches trending words, stories, and documents in parallel') and frames the tool as a unified superset across all crypto projects. It explicitly positions itself relative to the sibling `trending_stories_tool`, so an agent can distinguish the two without opening either 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?

There is a dedicated 'When to use vs `trending_stories_tool`' section that names the alternative, states the condition that selects it ('if only trending stories are needed'), gives the exclusion ('Do not call both tools for the same question'), and shows how to drop unneeded halves via `include_words`/`include_stories`. 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 Santiment tools Inspect

Try in Browser