Skip to main content
Glama
Sign In
X MCP Server

X MCP Server

by siddheshutd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get-tweets

Retrieve tweets by providing their IDs. Returns tweet data including text, author, and metrics.

Instructions

Get one or more tweets by their IDs

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": {
      "tweetIds": "<tweetIds>"
    },
    "name": "get-tweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
tweetIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as rate limits, authentication requirements, or whether the tool returns full tweet objects or partial data. The description merely restates the tool's purpose.

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 very brief but lacks front-loading of key information. It is under-specified, omitting critical details that would help an agent understand the tool's capabilities.

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 lack of annotations and output schema, the description should provide more context about what is returned. It only states the input mechanism, leaving the agent unaware of the output structure or any side effects.

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. It mentions 'by their IDs' but adds no further meaning, such as maximum number of IDs, format constraints, or behavior when an ID is invalid. The schema shows 'tweetIds' can be string or array, but the description does not clarify usage.

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 clearly states the tool retrieves tweets by their IDs, which is distinct from sibling tools like get-home-timeline or post-tweet. It specifies the resource (tweets) and the action (get) with the ID-based retrieval mechanism.

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 (e.g., search endpoints). No mention of prerequisites, limitations, or when not to use it.

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