Skip to main content
Glama
Sign In
twikit-mcp

twikit-mcp

by bintangtimurlangit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_trends

Fetch current Twitter trends for a selected category (trending, for-you, news, sports, entertainment). Specify count to control number of results.

Instructions

Get current trends for a category.

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
countNo
categoryNotrending

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states what the tool does but doesn't mention return format, pagination, rate limits, or any caveats. Since the verb 'get' implies a read operation, it is minimally informative but still lacks transparency about what the returned trends contain.

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?

The description is a single, front-loaded sentence with no waste. It is appropriately short for a simple getter, though it could add a bit more detail without becoming verbose. Overall, it is concise and structurally sound.

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?

Given the absence of annotations and output schema, the description is underspecified. It fails to explain what 'trends' represents or how the parameters affect output, leaving an agent uncertain about the return payload and parameter semantics. This is a simple tool, but completeness is still low.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the two parameters (count and category). It mentions 'category' but not 'count', giving no hint about how count affects results or the valid enum values. The description adds little meaning beyond the schema's structure.

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?

The description states a clear action ('Get') and resource ('trends') with a category qualifier, distinguishing it from sibling tools that focus on tweets, users, or direct messages. However, it lacks an explicit differentiator from other list-style tools, as no sibling explicitly mentions 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?

The description offers no guidance on when to use this tool over alternatives, such as search_tweets or get_home_timeline. It neither mentions prerequisites nor excludes inappropriate contexts. The single sentence provides no contextual usage direction.

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