unfollow_user
Unfollow a Threads user by user ID to manage your following list and maintain a targeted audience.
Instructions
Unfollow a user
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | User ID to unfollow |
Unfollow a Threads user by user ID to manage your following list and maintain a targeted audience.
Unfollow a user
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | User ID to unfollow |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only says 'Unfollow a user' without disclosing effects, permission requirements, reversibility, or response behavior, which is insufficient for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It is appropriately sized for a simple one-parameter tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple and the schema is complete, but with no annotations and no mention of outcomes or alternative tools, the minimal description leaves some gaps. It is adequate but not thorough.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully documents the single user_id parameter with a description, achieving 100% coverage. The tool description adds no additional meaning beyond what the schema already provides, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb 'Unfollow' with a clear resource ('a user'), and it is distinguishable from sibling tools like follow_user and block_user. It states exactly what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as follow_user or block_user. There are no context hints, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/baguskto/threads-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server