Skip to main content
Glama
Sign In
Grok MCP Server

Grok MCP Server

by guzus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_trends

Fetch trending topics and hashtags from X.com for any location. Specify location and number of results (up to 50).

Instructions

Get trending topics and hashtags on X.com

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_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNoLocation for trending topics (e.g., 'United States', 'Global')
max_resultsNoMaximum number of trends to return (1-50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states the basic action without mentioning any behavioral traits such as authentication requirements, rate limits, or what happens when no trends are available.

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?

A single sentence with no unnecessary words. It is appropriately front-loaded and concise for a simple tool, every word earns its place.

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

Completeness3/5

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

Given no output schema, the description implies the result is a list of trending topics and hashtags, which is somewhat complete. However, it lacks specifics on the structure of the return value, leaving some ambiguity.

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%, meaning both parameters (location, max_results) are already described in the schema. The description adds no additional meaning beyond the schema, meriting the baseline score of 3.

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 clearly states 'Get trending topics and hashtags on X.com', using a specific verb (Get) and resource (trending topics and hashtags). It distinguishes itself from sibling tools like search_posts, which focus on searching rather than trending content.

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?

No guidance on when to use this tool versus alternatives. The description only explains what it does, leaving the agent to infer appropriate contexts without explicit exclusions or recommendations.

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

Deploy Server

Other Tools