Skip to main content
Glama
moria97
by moria97

list-tv-reviews

Retrieve TV show reviews from Douban by providing the show's ID to analyze audience feedback and ratings.

Instructions

list tv reviews

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesdouban tv id, e.g. "1234567890"

Implementation Reference

  • The handler function for the "list-tv-reviews" tool. It validates the input 'id', fetches TV reviews via getTVReviews, formats them into a markdown table using json2md, and returns the content as text.
    async (args) => {
      if (!args.id) {
        throw new McpError(ErrorCode.InvalidParams, "douban tv id must be provided")
      }
    
      const reviews = await getTVReviews({ id: args.id })
      const text = json2md({
        table: {
          headers: ['title', 'rating', 'summary', 'id'],
          rows: reviews.map(_ => ({
            id: _.id,
            title: _.title,
            rating: `${_.rating?.value || 0} (有用:${_.useful_count || 0}人)`,
            summary: _.abstract
          }))
        }
      })
    
      return {
        content: [{ type: "text", text }]
      }
    }
  • Zod input schema defining the required 'id' parameter (Douban TV ID).
    {
      id: z.string().describe('douban tv id, e.g. "1234567890"')
    },
  • src/index.ts:152-180 (registration)
    MCP server.tool registration for 'list-tv-reviews', including name, description, schema, and handler function.
    server.tool(
      'list-tv-reviews',
      "list tv reviews",
      {
        id: z.string().describe('douban tv id, e.g. "1234567890"')
      },
      async (args) => {
        if (!args.id) {
          throw new McpError(ErrorCode.InvalidParams, "douban tv id must be provided")
        }
    
        const reviews = await getTVReviews({ id: args.id })
        const text = json2md({
          table: {
            headers: ['title', 'rating', 'summary', 'id'],
            rows: reviews.map(_ => ({
              id: _.id,
              title: _.title,
              rating: `${_.rating?.value || 0} (有用:${_.useful_count || 0}人)`,
              summary: _.abstract
            }))
          }
        })
    
        return {
          content: [{ type: "text", text }]
        }
      }
    )
  • Helper function getTVReviews that queries the Douban Frodo API for TV reviews given the TV ID and returns the reviews array.
    // 获取电视剧长评列表
    export async function getTVReviews(params: {
      id: string
    }) {
      const res = await requestFrodoApi(`/tv/${params.id}/reviews`);
      return res?.reviews ? res.reviews : []
    }
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, what permissions might be needed, how results are returned (e.g., pagination, format), or any rate limits. The description fails to add any behavioral context beyond the basic action implied by 'list'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with just two words, making it front-loaded and free of unnecessary information. While this conciseness comes at the cost of completeness, it efficiently communicates the core action without waste.

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?

Given the lack of annotations and output schema, the description is incomplete for effective tool use. It doesn't explain what the tool returns (e.g., review details, ratings, authors), how results are structured, or any behavioral traits. For a tool with one parameter but no output information, this leaves significant gaps in understanding.

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?

The input schema has 100% description coverage, with the single parameter 'id' clearly documented as a 'douban tv id'. The description adds no additional parameter information beyond what the schema provides, which meets the baseline score of 3 when schema coverage is high.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'list tv reviews' is essentially a tautology that restates the tool name without adding meaningful context. It specifies the verb 'list' and resource 'tv reviews', but lacks any distinguishing details about scope, format, or how it differs from sibling tools like 'list-movie-reviews' or 'list-book-reviews'.

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

Usage Guidelines1/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. It doesn't mention prerequisites, context for usage, or differentiate from similar tools like 'list-movie-reviews' or 'search-movie', leaving the agent with no usage direction.

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/moria97/douban-mcp'

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