Skip to main content
Glama

Search film MCP servers

search_film_mcps
Read-onlyIdempotent

Search the mcp.film directory of MCP servers for AI filmmaking. Filter by free-text query (matches name, vendor, tagline, description, capabilities, tools, category, pricing, auth, and the creative apps a server drives by name or alias, e.g. 'c4d' or 'resolve'), category id, or capability. Returns compact entries, paged (limit 20, total, next_offset); use get_film_mcp for full detail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_film_mcps"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1-100. Default 20.
queryNoFree-text search, e.g. 'upscale video' or 'voice cloning'
offsetNoStart index for paging; use next_offset from the previous call.
categoryNoCategory id (see list_film_categories)
capabilityNoExact capability tag, e.g. 'image-to-video'
remote_onlyNoOnly hosted remote MCPs (no local install)
official_onlyNoOnly vendor-maintained servers
answering_onlyNoOnly listings whose hosted endpoint answered mcp.film's anonymous MCP check in the last 7 days (evidence: endpoint_answered; a sign-in challenge counts as answering).
include_inactiveNoAlso return listings whose status is dead, archived or deprecated. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / answering_only
      Added value: +{
      +  "description": "Only listings whose hosted endpoint answered mcp.film's anonymous MCP check in the last 7 days (evidence: endpoint_answered; a sign-in challenge counts as answering).",
      +  "type": "boolean"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / include_inactive
      Added value: +{
      +  "description": "Also return listings whose status is dead, archived or deprecated. Default false.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size, 1-100. Default 20.",
      +  "type": "number"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Start index for paging; use next_offset from the previous call.",
      +  "type": "number"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent search. The description adds useful behavioral context: results are compact, paged with limit 20, total, and next_offset, and the free-text query matches many fields including creative app aliases.

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 front-loaded and dense with useful information: search scope, filter types, return format, paging, and the sibling alternative. No sentence is wasted.

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

Completeness4/5

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

Given nine optional parameters and no output schema, the description does enough by explaining the compact paged return shape and the detail alternative. The remaining filter semantics are covered by the fully populated input schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds value by explaining the breadth of free-text matching and the aliases it covers, and by clarifying the paged return shape with limit, total, and next_offset.

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 states a specific verb and resource: search the mcp.film directory of MCP servers for AI filmmaking. It also distinguishes the tool from the detail-oriented sibling by saying to use get_film_mcp for full detail.

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?

It clearly indicates the search use case and names get_film_mcp as the alternative for full detail. It does not explicitly contrast with recommend_film_mcps or plan_film_stack, but the context is still clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.