Social Fetch

List following ids of a Twitter profile

twitter_profile_following_ids_list

Read-only

List numeric user ids of accounts an X profile follows. Accepts a handle or numeric user id. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema

Name	Required	Description
`by`	No	Treat the path value as a handle or a numeric user id. Defaults to id when the value is all digits.
`trim`	No	Ignored if this tool does not support it.
`urls`	No	Alias for `handle`. Prefer `handle`.
`user`	No	Alias for `handle`. Prefer `handle`.
`limit`	No	Requested page size (1–5000).
`cursor`	No	Opaque pagination cursor returned by a previous response.
`handle`	No	X (Twitter) profile handle without the leading @, or a numeric user id.
`offset`	No	Ignored if this tool does not support it.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`pageSize`	No	Ignored if this tool does not support it.
`userName`	No	Alias for `handle`. Prefer `handle`.
`username`	No	Alias for `handle`. Prefer `handle`.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`maxResults`	No	Ignored if this tool does not support it.
`profileUrl`	No	Alias for `handle`. Prefer `handle`.
`linkedinUrl`	No	Alias for `handle`. Prefer `handle`.
`max_results`	No	Ignored if this tool does not support it.
`screen_name`	No	Alias for `handle`. Prefer `handle`.
`conversation_id`	No	Echo 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.

Changed18 schema fields changedSep 21, 2026

addedInput schema / properties / linkedinUrl / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / linkedinUrl / type
```
Removed value: -"string"
```

addedInput schema / properties / maxResults

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / pageSize

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / profileUrl / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / profileUrl / type
```
Removed value: -"string"
```

addedInput schema / properties / screen_name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / screen_name / type
```
Removed value: -"string"
```

addedInput schema / properties / trim

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / urls

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `handle`. Prefer `handle`."
+}

addedInput schema / properties / user / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / user / type
```
Removed value: -"string"
```

addedInput schema / properties / userName / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / userName / type
```
Removed value: -"string"
```

addedInput schema / properties / username / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / username / type
```
Removed value: -"string"
```

Changed2 schema fields changedSep 20, 2026

addedInput schema / properties / linkedinUrl

Added value: +{
+  "description": "Alias for `handle`. Prefer `handle`.",
+  "type": "string"
+}

addedInput schema / properties / profileUrl

Added value: +{
+  "description": "Alias for `handle`. Prefer `handle`.",
+  "type": "string"
+}

AddedSep 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context: it returns numeric user ids, accepts both handle and numeric id input, and explicitly instructs agents to use a cursor when paginated—details not present in the annotations.

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 concise sentences with no filler. The primary purpose is front-loaded in the first sentence, and the second sentence covers input flexibility and pagination behavior efficiently.

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 list tool with no output schema, the description adequately states the return type ('numeric user ids', 'a list') and mentions cursor-based pagination. The schema carries the burden for the 19 parameters, and no critical invocation detail appears missing, though a slightly richer return-shape note would make it fully complete.

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%, so the parameters are already fully documented. The description's claim that the tool 'Accepts a handle or numeric user id' merely restates what the handle, by, and alias parameter descriptions already say, adding no new semantic value 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?

The description uses a specific verb-resource pair: 'List numeric user ids of accounts an X profile follows.' This clearly distinguishes it from siblings like twitter_profile_followers_ids_list (followers vs following) and twitter_profile_following_list (ids vs richer profile data).

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 explicit guidance is given about when to use this tool versus alternatives such as twitter_profile_following_list or twitter_profile_followers_ids_list. The description does not state conditions, exclusions, or trade-offs, leaving selection to inference.

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

All Social Fetch 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.

List following ids of a Twitter profile

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources