Skip to main content
Glama
Positronikal

DaVinci MCP Professional

by Positronikal

switch_page

Navigate directly to any workspace in DaVinci Resolve, including Media, Cut, Edit, Fusion, Color, Fairlight, and Deliver pages, for efficient project workflow management.

Instructions

Switch to a specific page in DaVinci Resolve

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesThe page to switch to

Implementation Reference

  • Core handler: The switch_page method on DaVinciResolveClient. It validates the page name against allowed pages (media, cut, edit, fusion, color, fairlight, deliver), then calls self._resolve.OpenPage(page.lower()) to switch the page in DaVinci Resolve.
    def switch_page(self, page: str) -> bool:
        """Switch to a specific page."""
        self._ensure_connected()
    
        valid_pages = [
            "media",
            "cut",
            "edit",
            "fusion",
            "color",
            "fairlight",
            "deliver",
        ]
        if page.lower() not in valid_pages:
            raise ValueError(f"Invalid page. Must be one of: {', '.join(valid_pages)}")
    
        if self._resolve:
            return bool(self._resolve.OpenPage(page.lower()))
        return False
  • Tool dispatch in _call_tool: Routes the 'switch_page' MCP tool name to self.resolve_client.switch_page(), passing the 'page' argument from the request.
    async def _call_tool(self, name: str, arguments: dict[str, Any]) -> Any:
        """Dispatch a tool call to the resolve client."""
        if name == "get_version":
            return self.resolve_client.get_version()
        elif name == "get_current_page":
            return self.resolve_client.get_current_page()
        elif name == "switch_page":
            return self.resolve_client.switch_page(arguments.get("page", ""))
  • Schema registration: Defines the switch_page tool with name, description, and inputSchema requiring a 'page' string parameter with an enum of allowed page values (media, cut, edit, fusion, color, fairlight, deliver).
    types.Tool(
        name="switch_page",
        description="Switch to a specific page in DaVinci Resolve",
        inputSchema={
            "type": "object",
            "properties": {
                "page": {
                    "type": "string",
                    "description": "The page to switch to",
                    "enum": [
                        "media",
                        "cut",
                        "edit",
                        "fusion",
                        "color",
                        "fairlight",
                        "deliver",
                    ],
                }
            },
            "required": ["page"],
        },
    ),
  • Helper _ensure_connected: Called by switch_page to verify connection to DaVinci Resolve before executing the page switch.
    def _ensure_connected(self) -> None:
        """Ensure we're connected to Resolve."""
        if not self._is_connected:
            raise DaVinciResolveConnectionError("Not connected to DaVinci Resolve")
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing side effects (e.g., if already on the page), error conditions, or behavior beyond the basic switch.

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, front-loaded sentence of 10 words with no redundant information, perfectly concise.

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?

Given the tool's simplicity (one required enum parameter, no output schema), the description fully covers the necessary context for an agent to understand its purpose and usage.

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 has 100% coverage with enum descriptions. The description adds no extra meaning about the page parameter beyond what schema provides, so baseline 3 is appropriate.

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 verb 'switch' and resource 'page', and specifies the context 'in DaVinci Resolve'. It distinguishes from sibling tools like 'get_current_page' which reads the current page.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as 'switch_timeline' or 'get_current_page'. No prerequisites or context of use 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/Positronikal/davinci-mcp-professional'

If you have feedback or need assistance with the MCP directory API, please join our Discord server