Skip to main content
Glama
Sign In
twikit-mcp

twikit-mcp

by tangivis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

follow_user

Follow a Twitter user by their screen name.

Instructions

Follow a user by screen name.

Note: X aggressively rate-limits follow / unfollow — avoid bulk usage or your account may be temporarily restricted.

Args: screen_name: Twitter username (without @).

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": {
      "screen_name": "<screen_name>"
    },
    "name": "follow_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
screen_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.33

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that X aggressively rate-limits follow/unfollow and that bulk usage may lead to temporary restrictions. This is valuable behavioral context beyond the tool's basic function.

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?

The description is extremely concise: two sentences for the purpose and warning, followed by an Args line. Every word serves a purpose, and the critical information is front-loaded.

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 single-parameter action tool with no annotations, the description covers purpose, usage guidelines, and parameter format. It does not describe the return value, but the tool is simple and the context is sufficient for correct invocation.

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

Parameters4/5

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

The schema has 0% description coverage, so the description compensates. It clarifies that screen_name expects a Twitter username without the '@' symbol, adding meaning beyond the schema's type and title.

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 'Follow a user by screen name' clearly states the action (follow) and the target (user) and the method (by screen name). It distinguishes itself from siblings like 'unfollow_user' and 'mute_user', making the tool's purpose unambiguous.

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

Usage Guidelines4/5

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

The description explicitly warns about aggressive rate limiting and advises against bulk usage, which provides important usage context. However, it does not specify when not to use or list alternatives, though for this simple action, the guidance is adequate.

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