Skip to main content
Glama

XCROP X (Twitter) data

Get trending topics

get_trending
Read-only

Trending topics on X, worldwide or for a country. Costs 100 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoCountry name or code, e.g. United States or US; omit for worldwide

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The 100-credit cost is genuinely useful context that annotations do not carry, letting an agent weigh the call against cheaper siblings. Annotations already declare readOnlyHint and openWorldHint, so the remaining gaps (freshness, number of topics returned, rate limits) are less critical.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero waste; the resource and scope come first and the cost caveat follows. Nothing is repeated or padded.

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?

For a simple one-parameter read tool with full schema coverage, annotations, and no output schema, the description covers what it returns and what it costs. It stops short of describing result shape or freshness, which would be the only remaining additions an agent might want.

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?

With a single parameter at 100% schema coverage, the schema already documents that omitting country yields worldwide results. The description restates the same worldwide/country distinction without adding accepted formats, default behavior nuance, or examples beyond what the schema provides.

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?

"Trending topics on X" names a specific resource and verb-less action, and "worldwide or for a country" pins down the scope. No sibling in the list covers trending topics, so it is distinguishable by resource alone, though the description never explicitly contrasts itself with the search tools.

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

Usage Guidelines3/5

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

The phrase "worldwide or for a country" implies how to choose the scope via the country parameter, which is a weak form of usage guidance. It never says when to reach for this instead of search_tweets or get_user_tweets, and there are no stated prerequisites or exclusions.

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