Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Twitter profile subscriptions

twitter_profile_subscriptions_list
Read-onlyIdempotent

Retrieve the creator accounts an X profile subscribes to by handle or numeric user ID, with cursor support for paginated results.

Instructions

List creator accounts an X profile subscribes to, by handle or numeric user id. Requires handle. Returns a list (use cursor when paginated).

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "twitter_profile_subscriptions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoTreat the path value as a handle or a numeric user id. Defaults to id when the value is all digits.
cursorNoOpaque pagination cursor returned by a previous response.
handleYesRequired. X (Twitter) profile handle without the leading @, or a 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 only the pagination hint ('use cursor when paginated'); it does not mention the schema-level sequencing constraint around conversation_id or the lack of parallel calls, and 'Requires `handle`' merely restates the schema's required field.

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?

Two short sentences with the resource named first and the required input and return shape front-loaded. The clause 'Requires `handle`' is slightly redundant with the schema's required array but costs little.

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 no output schema, the description does state the return shape ('a list') and points to cursor pagination, which is the main thing an agent needs. It could say more about what fields each subscription entry contains or an ordering, but nothing critical for correct invocation is missing given full schema coverage and rich annotations.

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 schema already explains by/handle/cursor/context/llm_model/conversation_id in detail. The description echoes handle and cursor without adding format or semantics beyond that, so the baseline 3 applies.

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: lists creator accounts an X profile subscribes to, and clarifies the subject can be addressed by handle or numeric id. An agent can distinguish this from twitter_profile_following_list (accounts the profile follows) via the word 'subscribes', though the description never names that sibling explicitly.

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?

Gives the key precondition ('Requires `handle`') and a hint about cursor use when paginated, but offers no explicit when-to-use versus alternatives such as following_list or followers_list. Guidance is implied rather than stated.

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