AIsa X / Twitter

Get Trends By Woeid

get_twitter_trends

Read-onlyIdempotent

Get the trending topics for a location, identified by its Yahoo WOEID (Where On Earth ID), with an optional count (default 30). Use this for a real-time read on what a specific market is talking about right now — useful for timing content or spotting emerging stories. Returns trend names and volumes under trends. Once you pick a trend, search its posts with get_twitter_tweet_advanced_search.

Usage-based billing; Default request estimate: $0.00015 USD (not a fixed price). Declared unit rate: $0.00001 USD per provider_credit. Account-specific pricing and final settlement may differ.

Input Schema

Name	Required	Description	Default
`count`	No	The number of trends to return. Default is 30. Provider reference (supplier schema): `{"default":30,"format":"int64","minimum":30,"type":"integer"}`.
`woeid`	No	The WOEID of the location. Example: 2418046. Provider reference (supplier schema): `{"format":"int64","type":"integer"}`.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

addedInput schema / properties / count / description

Added value: +"The number of trends to return. Default is 30.\n\nProvider reference (supplier schema): `{\"default\":30,\"format\":\"int64\",\"minimum\":30,\"type\":\"integer\"}`."

addedInput schema / properties / woeid / description

Added value: +"The WOEID of the location. Example: 2418046.\n\nProvider reference (supplier schema): `{\"format\":\"int64\",\"type\":\"integer\"}`."

Changed9 schema fields changedOct 15, 2026
- removedInput schema / properties / count / default
```
Removed value: -30
```
- removedInput schema / properties / count / description
```
Removed value: -"The number of trends to return. Default is 30."
```
- removedInput schema / properties / count / format
```
Removed value: -"int64"
```
- removedInput schema / properties / count / minimum
```
Removed value: -30
```
- changedInput schema / properties / count / type
```
Previous value: -"integer"New value: +"string"
```
- removedInput schema / properties / woeid / description
```
Removed value: -"The WOEID of the location. Example: 2418046."
```
- removedInput schema / properties / woeid / format
```
Removed value: -"int64"
```
- changedInput schema / properties / woeid / type
```
Previous value: -"integer"New value: +"string"
```
- changedInput schema / required
```
Previous value: -[
-  "woeid"
-]New value: +[]
```
First observedSep 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety bar is pre-covered. The description adds useful context the annotations don't: the returned payload ('trend names and volumes under `trends`') and an account-specific pricing/usage note. It omits rate limits or freshness guarantees, but the additions are genuine.

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?

Purpose is front-loaded and the two core sentences are dense with no waste. The injected pricing block adds length that isn't part of the tool's intrinsic description, slightly diluting the otherwise tight structure.

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?

With a rich output schema and full annotation coverage, the description supplies what the agent still needs: the location semantics, the returned field group, and the downstream search tool. It leaves only minor gaps like pagination/freshness, which the output schema may cover.

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 coverage is 100%, so both params are already documented; the description largely restates WOEID and the default `count` of 30 rather than adding syntax or format meaning. Baseline 3 applies when the schema carries the parameter burden.

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 verb and resource ('Get the trending topics for a location') and pins the identifier (Yahoo WOEID), distinguishing it from the sibling tweet/user tools without ambiguity. It also names the natural next step tool, making its role in the workflow unmistakable.

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?

It gives a clear scenario ('real-time read on what a specific market is talking about right now', 'timing content or spotting emerging stories') and routes the follow-up to `get_twitter_tweet_advanced_search`. However, it never states when NOT to use it or how it relates to other trend-adjacent siblings, so it stops short of full explicit routing.

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

All AIsa X / Twitter 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?