Skip to main content
Glama
achenglike

ThePornDB MCP Service

by achenglike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
tokenNoThePornDB API token (uses default public token if not provided)
log-levelNoLogging level: DEBUG, INFO, WARNING, ERRORINFO
transportNoMCP transport: stdio, streamable-httpstdio

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_scenesB
Search for adult video scenes by term and optional year.

Args:
    search_term: Search query (scene title, performer name, site name)
    year: Optional filter by release year (1900-current year)
    ctx: MCP context (injected automatically)

Returns:
    SearchResponse with paginated scene results

Raises:
    CallToolResult: With error if validation fails
search_moviesB
Search for full-length movies by term and optional year.

Args:
    search_term: Search query (movie title, series, studio)
    year: Optional filter by release year (1900-current year)
    ctx: MCP context (injected automatically)

Returns:
    SearchResponse with paginated movie results

Raises:
    CallToolResult: With error if validation fails
search_javA
Search for Japanese Adult Video content by term and optional year.

Args:
    search_term: Search query (JAV title, code, performer name)
    year: Optional filter by release year (1900-current year)
    ctx: MCP context (injected automatically)

Returns:
    SearchResponse with paginated JAV results

Raises:
    CallToolResult: With error if validation fails
get_content_detailsA
Get complete details for a specific content item by ID.

Args:
    content_id: Unique content identifier
    content_type: Content type ("scene", "movie", or "jav")
    ctx: MCP context (injected automatically)

Returns:
    MediaData with complete content details

Raises:
    CallToolResult: With error if validation fails or content not found
search_performersC
Search for performers by name.

Args:
    name: Performer name to search
    ctx: MCP context (injected automatically)

Returns:
    SearchResponse with performer results

Raises:
    CallToolResult: With error if validation fails
get_performer_detailsA
Get complete performer profile with bio, measurements, aliases, and external links.

Args:
    performer_id: Unique performer identifier
    ctx: MCP context (injected automatically)

Returns:
    Dictionary with complete performer details

Raises:
    CallToolResult: With error if validation fails or performer not found

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. The tools are organized by resource type (content, performer) and action (get details, search), with specific tools for different content categories (JAV, movies, scenes) that have clear boundaries.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern throughout. The naming convention is perfectly uniform with 'get_' for retrieval operations and 'search_' for search operations, followed by the specific resource type.

Tool Count5/5

Six tools is well-scoped for this adult content database service. Each tool earns its place by covering distinct aspects of the domain: detailed retrieval for content and performers, plus specialized search functions for different content types and performers.

Completeness4/5

The tool surface provides excellent coverage for search and retrieval operations across the main domain entities. Minor gaps exist such as no update/delete operations (which may be intentional for a read-only API) and no content creation tools, but the core query functionality is comprehensive.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources