Skip to main content
Glama
Sign In
Enterprise Threads MCP Server

Enterprise Threads MCP Server

by baguskto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_user_following

Retrieve the list of accounts a specific Threads user follows. Specify user ID and optional limit to get their following list for audience analysis and management.

Instructions

Get following list for a user

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_user_following"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of following to retrieve
user_idNoUser ID to get following for (defaults to current user)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the action without revealing behaviors such as pagination, sorting, authentication requirements, privacy filtering, or the shape of the returned list.

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?

The description is a single, front-loaded sentence that is easy to parse. While it is concise, it is also under-specified; however, it does not waste words and earns its place as a minimal statement.

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 output schema and no annotations, the description does not convey return format, pagination, error handling, or any list-specific details. For an endpoint that returns a list, this lack of context leaves the agent under-informed about the tool's actual behavior.

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 'limit' and 'user_id' having descriptions, so the schema already provides parameter semantics. The description adds no additional insight beyond what the schema states, such as the default behavior of user_id.

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?

The description uses a specific verb ('Get') and clearly identifies the target resource ('following list for a user'). It distinguishes from sibling 'get_user_followers' by the direction of the relationship (following vs followers), though it does not explicitly call out that distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_user_followers' or 'follow_user'. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name.

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