Skip to main content
Glama
Sign In
Twitter241 MCP Server

Twitter241 MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_about_account

Retrieve detailed account information for any Twitter user by providing their username. Get profile details like bio, followers, and more.

Instructions

Get About Account

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": {
      "username": "<username>"
    },
    "name": "get_about_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesExample value: MrBeast

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

D1.4/5.0
Behavior1/5

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It reveals nothing about what happens when called, such as whether it returns profile metadata, requires authentication, or has side effects. The description is a pure tautology.

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 but under-specified, not genuinely concise. The single sentence 'Get About Account' merely repeats the title and fails to earn its place by adding any informative content.

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?

Despite having only one parameter and no output schema, the tool needs at least a basic explanation of what 'About Account' means and what it returns. With multiple sibling tools that likely overlap, the complete lack of contextual information makes this description wholly inadequate.

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% because the username parameter has a description (example value: MrBeast). According to the rubric, baseline is 3 when coverage is high, even though the tool description adds no parameter meaning beyond the schema. The example value is minimal but technically present.

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 About Account' is a direct restatement of the tool name, offering no specific verb+resource clarity or differentiation from siblings like get_user_by_username or get_user_tweets. It fails to state what 'About Account' contains or what kind of data is retrieved.

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?

No guidance is provided on when to use this tool versus the many sibling tools that fetch user or account data. The description gives no context about the appropriate scenario, prerequisites, or alternatives.

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