Skip to main content
Glama
Sign In
Desearch MCP Server

Desearch MCP Server

Official
by Desearch-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get X Trends

x-trends
Read-only

Retrieve trending topics on X (Twitter) for a location by its WOEID. Provide a WOEID and optional count to get current regional trends.

Instructions

Retrieve trending topics on X (Twitter) for a location by its WOEID using Desearch.

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 (30-100).
woeidYesWOEID of the location, example: 23424977 for the United States.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and scope profile is covered. The description adds only that results come from Desearch, and says nothing about rate limits, freshness of trends, or failure modes.

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?

One sentence with zero filler, front-loading the action and resource before the input mechanism. Nothing is redundant 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 read-only two-parameter tool with no output schema and full schema coverage, the description is nearly complete. It could note what a trend entry looks like or whether count defaults, but nothing critical to correct invocation is missing.

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%: both woeid and count are documented in the schema with ranges and an example. The description adds no syntax or format detail beyond repeating the WOEID requirement, so the baseline 3 applies.

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?

States a specific verb (retrieve) and resource (trending topics on X/Twitter), plus the scoping mechanism (location via WOEID). It does not explicitly name a sibling, but no sibling covers trends, so it is implicitly distinct.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusions; the only added detail is the data source (Desearch). An agent must infer usage entirely from the name and the WOEID requirement.

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