AIsa X / Twitter

Check Follow Relationship

get_twitter_user_check_follow_relationship

Read-onlyIdempotent

Check whether one X user follows another, in both directions, by @handle. Use this for a single targeted lookup instead of paging through get_twitter_user_followers or get_twitter_user_followings — it answers 'does A follow B, and does B follow A' in one request. Returns the relationship flags under data.

Published reference price: $0.001 USD per successful request. Account-specific pricing and final settlement may differ.

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": "get_twitter_user_check_follow_relationship"
  }
}

Input Schema

Name	Required	Description	Default
`source_user_name`	Yes	Screen name of the source user.
`target_user_name`	Yes	Screen name of the target user.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it answers both directions (A→B and B→A) in a single request and returns the flags under `data`. The pricing disclosure adds cost context. Minor gap: no note on what happens when a handle doesn't exist or when accounts are protected/private.

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?

Front-loaded with the core behavior followed by the routing advice, with no redundant sentences. The injected pricing block inflates the text slightly but is boilerplate rather than author padding.

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?

With annotations, full schema coverage, and an output schema present, the description needn't explain return values, yet it usefully points to `data`. Routing to alternatives and bidirectional semantics are covered. Edge-case behavior (nonexistent/private accounts) is the only material omission.

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 coverage is 100%, with both source_user_name and target_user_name documented as screen names, so the baseline is 3. The description only adds 'by @handle', a small hint on identifier format, but does not clarify directionality mapping (which param is the follower vs. the followed) beyond the schema.

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?

States a specific verb (check), resource (follow relationship), and scope (one X user follows another, both directions, by @handle). It explicitly names the sibling tools it is not (get_twitter_user_followers / get_twitter_user_followings), so an agent can distinguish it without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: 'Use this for a single targeted lookup instead of paging through...'. Names the alternatives and the condition (single targeted lookup vs. paging), leaving nothing to inference.

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

All AIsa X / Twitter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?