Skip to main content
Glama

Tmdb

by io.github.pipeworx-io

Search Person

search_person
Read-onlyIdempotent

Search TMDB for actors, directors, or crew members by name. Returns person name, popularity, known-for department, profile path, and TMDB person_id needed by person and person_combined_credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
queryYes
languageNo
include_adultNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoCurrent page number
resultsNoArray of person search results
total_pagesNoTotal number of pages available
total_resultsNoTotal number of results

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Leonardo DiCaprio"
+  },
+  {
+    "page": 1,
+    "query": "Meryl Streep"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "results": {
+      "description": "Array of person search results",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Person ID",
+            "type": "number"
+          },
+          "known_for": {
+            "description": "Known works",
+            "type": "array"
+          },
+          "name": {
+            "description": "Person name",
+            "type": "string"
+          },
+          "popularity": {
+            "description": "Popularity score",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_pages": {
+      "description": "Total number of pages available",
+      "type": "number"
+    },
+    "total_results": {
+      "description": "Total number of results",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds no behavioral details beyond what annotations provide, but does not contradict them.

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?

The description is two sentences long, front-loaded with purpose and return structure. Slightly brief but no 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?

With 4 parameters and no schema descriptions, the description fails to cover pagination, language filtering, or adult content option. Output schema exists but return fields are only partially mentioned.

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 coverage is 0%, yet the description only discusses 'query' implicitly via examples. It does not explain 'page', 'language', or 'include_adult', leaving three parameters undocumented.

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

Purpose5/5

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

The description clearly states the tool searches TMDB for people by name and lists return fields. It distinguishes from siblings like search_movie, search_tv, and search_multi by focusing on people and referencing dependent tools.

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 description implies this tool is for finding person data needed by 'person' and 'person_combined_credits' but does not explicitly state when to prefer it over siblings like search_multi or provide exclusions.

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

All Tmdb toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

The tool set blends two unrelated domains (TMDB and Pipeworx). Among Pipeworx tools, several overlap heavily (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, suggest_questions) with vague boundaries, making it hard for an agent to pick the right one. TMDB tools are distinct but the overall mixture creates confusion about which domain a request belongs to.

Naming Consistency3/5

All tools use snake_case, which is consistent. However, naming styles vary widely: TMDB tools use simple noun or verb-first names (movie, search_movie, discover_tv), while Pipeworx tools use longer descriptive phrases with prefixes (ask_pipeworx, polymarket_arbitrage, entity_profile). The pattern is not predictable across the set.

Tool Count2/5

50 tools is excessive for a server named 'Tmdb'. Only about 18 tools are actually TMDB-related; the remaining 32 belong to the Pipeworx ecosystem. This inflates the count and makes the server feel bloated and unfocused, far beyond a well-scoped TMDB server.

Completeness3/5

The TMDB portion is quite complete (search, discover, details, credits, recommendations, trending, genres, configuration). However, the server's overall scope is muddled—it tries to cover two disjoint domains, so no single domain feels fully fleshed out. There are also some missing TMDB features (e.g., upcoming/now playing) that would require extra discovery. The Pipeworx tools cover data broadly but overlap in coverage.

Resources