Twitter241 MCP Server

get_trends_by_location

Find location-specific trending topics by providing a WOEID. Optionally exclude hashtags to refine results.

Instructions

Get Trends By 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": "get_trends_by_location"
  }
}

Input Schema

Name	Required	Description	Default
`woeid`	Yes	This value can be gotten from the Get Available Trends Locations endpoint.
`exclude`	No	Setting this value equal to hashtags will remove all hashtags from the response list.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

D1.4/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It provides none: no mention of return format, side effects, limits, or prerequisites. The description is just a restatement of the name and offers zero transparency.

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

Conciseness2/5

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

The description is extremely short (four words), but this is under-specification, not conciseness. It contains no useful information and fails to even hint at the tool's purpose beyond the name.

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

Completeness1/5

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

For a tool with 2 parameters, no annotations, and no output schema, the description is completely inadequate. It does not explain what trends are returned, how the location is specified, what the response looks like, or any constraints. The tool cannot be effectively used based solely on this description.

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% with descriptions for both parameters. The woeid description usefully points to the Get Available Trends Locations endpoint, and exclude explains its effect. However, these descriptions are minimal and the tool description itself adds no parameter semantics beyond what the schema already provides.

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

Purpose1/5

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

The description 'Get Trends By Location' is a direct tautology of the tool name. It provides no additional detail about what trends are, what 'by location' means, or how it differs from sibling tools like get_available_trends_locations.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. The parameter description for woeid mentions it can be gotten from the Get Available Trends Locations endpoint, but this is not framed as usage guidance and no explicit when/when-not is provided.

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

Deploy Server