Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Check Twitter follow relationship

twitter_friendship_get
Read-onlyIdempotent

Check whether one X account follows another using handles or numeric user IDs. Provide source and target accounts to verify a follower relationship.

Instructions

Check whether one X account follows another, by handles or numeric user ids. Requires source and target.

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": "<source>",
      "target": "<target>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "twitter_friendship_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoTreat source and target as handles or numeric user ids. Defaults to id when a value is all digits.
sourceYesSource account (the potential follower). Handle without the leading @, or numeric user id.
targetYesTarget account (the potential followee). Handle without the leading @, or numeric user id.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that identification works by handle or numeric id, but says nothing about the result shape (boolean flags per direction) or failure behavior for protected/suspended accounts.

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?

Two short sentences with zero padding; the core action is front-loaded and the requirement statement follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple pairwise lookup the annotations and rich schema cover most of the burden, but with no output schema the description never indicates what is returned (e.g., followed_by/following booleans), which is the main remaining gap an agent needs.

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%, including the by enum defaulting to id when values are all digits, so the schema already carries parameter meaning. The description only restates that source and target accept handles or ids, adding no semantics beyond it.

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?

States a specific verb and resource: checking whether one X account follows another, with the direction made explicit (source follows target via the schema). It is clearly distinguishable from list-style siblings such as twitter_profile_followers_list, though the description does not name them.

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

Usage Guidelines3/5

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

Conveys that both source and target are required and that identifiers may be handles or ids, which implies the call pattern. It gives no explicit when-to-use guidance versus the followers/following list tools, so an agent must infer that this is the pairwise check rather than a bulk listing.

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