Skip to main content
Glama

CheapXAPI — Twitter (X) Search, Tweets, Profiles & Followers MCP Server

x_trends

Get trends. Trending topics for a location.

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": "x_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of trends to return.
woeidYesLocation WOEID, e.g. `1` for worldwide, `23424977` for the United States.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It reveals that results are location-scoped, but says nothing about whether this is a read-only public endpoint, whether it requires authentication, how many trends come back by default, or what the response structure looks like (no output schema either).

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?

Two short sentences, front-loaded with the action and followed by the scope. Nothing is wasted, though the second sentence largely repeats the first's implication that these are location-specific.

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

Completeness2/5

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

For a two-parameter tool with no annotations and no output schema, the description is thin: it omits default count behavior, response shape, and any auth or rate-limit context. The schema does cover the parameters well, which keeps this from being a 1, but behaviorally an agent is left guessing.

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% and both parameters are documented in the schema, including WOEID examples (1 for worldwide, 23424977 for the US), so the description adds no parameter meaning of its own. Per the baseline rule for full schema coverage, this scores 3.

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

Purpose3/5

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

The description names a resource (trends) and a scope (trending topics for a location), so the verb+resource is identifiable, but the phrasing 'Get trends' is close to a restatement of the tool name and adds little beyond 'trending topics for a location'. It does not differentiate itself from any of the many x_* siblings, though none of those clearly cover trends.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The only contextual hint is the word 'location', which implies the tool is location-scoped, but it never says when an agent should prefer this over other X/Twitter data tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources