Tvmaze

Search People

search_people

Read-onlyIdempotent

Search TVMaze's actor/person database by name. Returns matched people with id, name, country code, birthday, deathday, gender, and headshot image URL.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Person name

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of results
`query`	Yes	Search query string
`results`	Yes	Array of matching people

Schema Changelog

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

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "Bryan Cranston"
+  },
+  {
+    "query": "Meryl Streep"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of results",
+      "type": "number"
+    },
+    "query": {
+      "description": "Search query string",
+      "type": "string"
+    },
+    "results": {
+      "description": "Array of matching people",
+      "items": {
+        "properties": {
+          "birthday": {
+            "description": "Birth date (YYYY-MM-DD)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "country": {
+            "description": "2-letter country code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "deathday": {
+            "description": "Death date (YYYY-MM-DD) or null",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "gender": {
+            "description": "Gender (Male, Female, etc)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "TVMaze person ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "image": {
+            "description": "Photo URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Person name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "score": {
+            "description": "Match score from search",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "tvmaze_url": {
+            "description": "TVMaze person page URL",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "count",
+    "results"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds value by listing the returned fields, but does not mention potential limitations like pagination or rate limits. No contradiction with annotations.

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 a single sentence that efficiently conveys purpose and output, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple search tool with one parameter and an existing output schema, the description covers all necessary context: it states the source, search method, and returned fields. No gaps.

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?

Schema coverage is 100% and the parameter description is minimal ('Person name'). The description adds context ('by name') and output fields, but these do not significantly enhance parameter understanding beyond the schema.

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 TVMaze's actor/person database by name and specifies the returned fields (id, name, country code, etc.). It distinguishes from sibling tool 'search_shows' which searches for shows.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for searching people by name, and examples clarify typical queries. It does not explicitly state when not to use it, but sibling tools like 'search_shows' provide context for differentiation.

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

All Tvmaze tools Inspect

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.