Skip to main content
Glama

CheapXAPI — Twitter (X) Search, Tweets, Profiles & Followers MCP Server

x_user_check_follow_relationship

Check follow relationship. Whether two users follow each other.

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": {
      "source_user_name": "<source_user_name>",
      "target_user_name": "<target_user_name>"
    },
    "name": "x_user_check_follow_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_user_nameYesScreen name of the first user.
target_user_nameYesScreen name of the second user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about auth needs, rate limits, or what the response contains (a boolean? a mutual/one-way breakdown? a user object?). The mutual-vs-one-way phrasing actually adds behavioral uncertainty.

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

Conciseness3/5

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

Two short sentences, nothing padded, and the core action is front-loaded. The second sentence is too terse to earn its place, reading as a restatement that raises a question instead of answering one.

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?

With no annotations, no output schema, and a boolean-style relationship check, the description needs to define direction and return semantics. Neither is present, so an agent cannot reliably interpret results without trial and error.

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 coverage is 100%, so the baseline is 3, but the direction mapping is the one thing the description should clarify: whether source_user_name is the follower or the followee. 'Two users follow each other' muddies rather than clarifies which parameter plays which role.

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

Purpose3/5

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

States a specific verb and resource ('Check follow relationship'), which separates it from the listing siblings like x_user_followers. However the second sentence, 'Whether two users follow each other,' introduces ambiguity about directionality rather than resolving it, so the agent still cannot say precisely what is being checked.

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 prefer this over x_user_followers, x_user_followings, or x_user_followers_ids — the obvious neighbors for relationship questions. The description gives no context, prerequisites, or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources