Skip to main content
Glama

get_user_doulist

Read-only

Fetch a Douban user's doulist collection by UID to inspect their saved lists. Provide the UID when no cookie is available.

Instructions

获取某用户的豆列清单。无 cookie 时必须传 uid。

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": {
      "uid": "<uid>"
    },
    "name": "get_user_doulist"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0-alpha.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description goes beyond that by disclosing an authentication dependency: behavior changes depending on whether a cookie/session exists, which is exactly the kind of auth context the annotations do not carry.

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 no filler; the purpose is front-loaded and the conditional requirement follows. It is terse to the point of under-specification rather than verbose.

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

Completeness3/5

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

For a simple read-only single-parameter tool with no output schema, the description covers purpose and auth condition adequately. It omits any disambiguation from get_user_collections and says nothing about the relationship between cookie-derived user and the uid argument.

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 0%, so the description carries the burden for the single uid parameter. It explains uid identifies the user and is conditionally required without a cookie, but gives no format or type detail, and it slightly conflicts with the schema's unconditional required:[uid].

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: fetch a given user's doulist (list-of-lists) inventory. It is clear what the tool returns, but it never distinguishes itself from the sibling get_user_collections, which an agent could easily confuse with 'doulist'.

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?

The second sentence gives a real prerequisite: pass uid when no cookie is present, which implies the cookie/session path. However, there is no guidance on when to pick this over get_user_collections or get_user_profile, so usage is only implied.

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