Skip to main content
Glama
moria97
by moria97

list-movie-reviews

Retrieve movie reviews from Douban by providing the movie ID to analyze audience feedback and critical perspectives.

Instructions

list movie reviews

Input Schema

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

Implementation Reference

  • MCP tool handler for 'list-movie-reviews': validates input ID, fetches movie reviews via getMovieReviews, formats results as a markdown table, and returns structured text content.
    async (args) => {
      if (!args.id) {
        throw new McpError(ErrorCode.InvalidParams, "douban movie id must be provided")
      }
    
      const reviews = await getMovieReviews({ 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 schema for input parameters of the 'list-movie-reviews' tool, requiring a douban movie ID.
    {
      id: z.string().describe('douban movie id, e.g. "1234567890"')
    },
  • src/index.ts:122-149 (registration)
    Registration of the 'list-movie-reviews' tool in the MCP server using server.tool, specifying name from TOOL enum, description, input schema, and handler function.
      TOOL.LIST_MOVIE_REVIEWS,
      "list movie reviews",
      {
        id: z.string().describe('douban movie id, e.g. "1234567890"')
      },
      async (args) => {
        if (!args.id) {
          throw new McpError(ErrorCode.InvalidParams, "douban movie id must be provided")
        }
    
        const reviews = await getMovieReviews({ 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 that performs the actual API request to fetch movie reviews from Douban's Frodo API endpoint.
    export async function getMovieReviews(params: {
      id: string
    }) {
      const res = await requestFrodoApi(`/movie/${params.id}/reviews`);
      return res?.reviews ? res.reviews : []
    }
  • TypeScript interface defining the expected structure of individual movie reviews returned by the API.
    interface MovieReview {
      id: string
      title: string
      alt: string
      subject_id: string
      author: {
        id: string
        name: string
        uid: string
        signature: string
        alt: string
        avatar: string
      }[]
      rating: {
        max: number
        numRaters: number
        average: string
        min: number
      }
      summary: string
    }
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether there are rate limits, pagination behavior, or what format the reviews are returned in. The description provides zero behavioral context beyond the basic action stated.

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 maximally concise at just three words. While this represents under-specification rather than ideal conciseness, within the scoring framework for this dimension, it's appropriately sized and front-loaded with zero wasted words. Every word earns its place in communicating the basic action.

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 this is a tool with one parameter but no annotations and no output schema, the description is inadequate. It doesn't explain what 'list' means operationally, what format reviews are returned in, whether there are constraints on the movie ID, or how this differs from sibling tools. For a tool that presumably returns structured data about reviews, the description provides insufficient context for effective use.

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 'douban movie id, e.g. "1234567890"'. The description adds no parameter information beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate since the schema does the heavy lifting for parameter documentation.

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 movie reviews' is a tautology that essentially restates the tool name with minimal added value. It specifies the verb 'list' and resource 'movie reviews', but doesn't distinguish this tool from its sibling 'list-book-reviews' or 'list-tv-reviews' beyond the resource type. While it communicates the basic action, it lacks specificity about what kind of listing this provides.

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 absolutely no guidance about when to use this tool versus alternatives. There are multiple sibling tools for listing reviews (book, tv) and searching movies, but the description doesn't indicate whether this is for a specific movie ID, whether it's comprehensive or filtered, or when to choose this over search-movie. No context, exclusions, or alternatives are mentioned.

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