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.

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": {
      "woeid": "<woeid>"
    },
    "name": "get_twitter_trends"
  }
}

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`	Yes	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.

Changed1 schema field changedNov 1, 2026
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "woeid"
+]
```

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, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that: the default of 30 trends, the shape of the response ('trend names and volumes under `trends`'), and billing/pricing context. Rate limits and WOEID lookup guidance are the remaining gaps.

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 operation and identifier, then usage, then return shape, then the follow-up tool — a logical ordering with no filler sentences. The appended pricing boilerplate is metadata rather than authored prose, but it does add bulk.

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 needn't be fully spelled out, and the description still names the `trends` field and its contents. For a two-parameter read tool with full annotation coverage, an agent has everything needed to invoke it correctly.

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 both parameters are already documented with defaults and an example. The description expands the WOEID acronym and restates the count default, which is helpful glossing but adds no new constraints beyond the schema. Baseline 3 applies.

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 to a Yahoo WOEID, with the optional count and its default stated inline. No sibling tool covers trends, so an agent can route to it immediately without opening the schema.

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?

Gives concrete usage context ('real-time read on what a specific market is talking about right now — useful for timing content or spotting emerging stories') and an explicit next step: search a picked trend via get_twitter_tweet_advanced_search. It stops short of stating when NOT to use it or what alternative to pick for historical trend data.

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?