Skip to main content
Glama

get_user_collections

Read-only

Retrieve a Douban user's movie or book wish, doing, or collected lists by UID, with optional count and start for pagination; UID is required without cookie.

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>",
      "category": "<category>",
      "status": "<status>"
    },
    "name": "get_user_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
countNo
startNo
statusYes
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / start / maximum
      Added value: +9007199254740991
  2. First observedv1.0.0-alpha.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered, but the description adds meaningful context the annotations do not: the cookie-vs-uid authentication dependency. It still omits pagination behavior (count/start defaults and the 30 cap) and any statement about result shape or ordering.

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, front-loaded with purpose and followed by the required-condition caveat; nothing is wasted. It is arguably too terse rather than padded, so the terseness itself is the weakness, not the structure.

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?

For a 5-parameter tool with 3 required parameters, no output schema, and zero schema-level descriptions, this definition is under-specified. An agent cannot infer page size semantics, the 30-item ceiling, or that category must be movie or book without inspecting the raw schema.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden and it does not. It explains uid's conditional requirement and maps the three status values (想看/在看/看过) to the status enum, but says nothing about category (movie vs book), count (default 15, max 30), or start — three of five parameters remain opaque.

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 states a specific verb and resource (获取某用户的列表) and enumerates the three collection types, which lets an agent distinguish it from siblings like get_user_doulist or get_user_profile. It stops short of explicitly naming which sibling to use instead, so it is clear but not fully differentiated.

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?

It gives one concrete usage condition — when no cookie is present, uid must be supplied — which is genuinely useful routing information. However, it offers no guidance on choosing between this and the other user-* list tools, nor on when to prefer search_book/search_movie.

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