Skip to main content
Glama
kingcos

fanfou-mcp

by kingcos

manage_friendship

Follow or unfollow a Fanfou user by user ID. Automatically sends a follow request if the target account is protected.

Instructions

管理用户关注状态

调用饭否 API 的 /friendships/create.json 或 /friendships/destroy.json 接口 来关注或取消关注指定用户。

注意:在执行关注操作前,会先调用 get_user_info 查询目标用户信息, 如果目标用户账号受保护(protected),关注操作将变为申请关注, 需要对方确认后才能生效。

Args: user_id: 目标用户的 ID action: 操作类型,"create" 表示关注,"destroy" 表示取消关注 confirm: 是否确认操作(二次确认参数)

Returns: 操作结果字典,包含: - 是否关注: 操作后的关注状态 - 操作结果: 操作是否成功的描述信息 - 操作类型: 执行的具体操作(关注/取消关注) - 用户信息: 目标用户的基本信息 - 特殊情况: 如果是受保护账号的关注申请,会包含相关提示

或者确认信息字典,包含:
- 需要确认: 是否需要用户确认
- 用户预览: 要操作的用户预览
- 确认提示: 如何进行确认的说明

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
actionYes
confirmNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Without annotations, the description discloses important behavior: it calls get_user_info first, and for protected accounts it becomes a follow request. It does not cover rate limits or auth needs, but the key side effects are explained.

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 well-structured with paragraphs and an Args/Returns section. It is slightly lengthy but each part earns its place. Minor redundancy, but generally efficient.

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

Completeness5/5

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

Given the tool's complexity and the presence of an output schema, the description covers the main use case, the special protected account scenario, and the confirm parameter. Return values are detailed, making it comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully explains each parameter: user_id, action ('create'/'destroy'), and confirm (secondary confirmation). This adds significant meaning 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 clearly states the tool's purpose as managing user follow status (关注/取消关注), using specific API endpoints. It distinguishes from sibling tools like manage_favorite and publish_status.

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

Usage Guidelines4/5

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

The description explains when to use the tool (to follow/unfollow) and provides context about protected accounts. However, it does not explicitly mention when not to use or suggest alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kingcos/fanfou-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server