Skip to main content
Glama
Sign In

ChatCut

by io.chatcut
OverviewDiscussionsAdmin

target_project

Bind this external MCP session to an existing ChatCut project.

Use this after list_projects when the user wants to continue work on an existing project, or when the connector starts without an active project. Subsequent project-scoped tools such as read_project, edit_item, read_script, and submit_export will target this project through the same external MCP session.

Use the returned timelineId/trackId as orientation for the currently active timeline and default video track. Call read_project for the project map, then use preview_timeline or inspect_item for the timeline scope you intend to edit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "target_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject ID or unique prefix from list_projects for the project to target.
editorBaseUrlNoEditor origin/base URL. Defaults to CHATCUT_EDITOR_URL or http://localhost:5173.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=false, so the agent knows this mutates session state; the description adds the non-obvious scope of that mutation — that it re-routes all subsequent project-scoped tools (read_project, edit_item, read_script, submit_export) in the same session. It omits failure behavior for an invalid projectId, keeping it below a 5.

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?

Purpose is front-loaded in one sentence, followed by usage conditions and then post-binding workflow. The third paragraph about read_project/preview_timeline is helpful but slightly long for what it contributes; still, every sentence carries usable routing information.

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?

There is no output schema, and the description compensates by naming the returned timelineId/trackId and explaining how to use them as orientation. Combined with the session-scoping effect and next-step guidance, it covers what an agent needs to call and follow up, with only error handling left unspecified.

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 description coverage is 100%, with both projectId (including unique-prefix support) and editorBaseUrl fully documented in the schema, so the baseline is 3. The description adds nothing about parameter syntax or the prefix-matching behavior beyond what the schema already states.

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 opening sentence names a specific verb and resource: "Bind this external MCP session to an existing ChatCut project." It clearly distinguishes itself from list_projects (the discovery step) and create_project (implied alternative for new projects), so an agent can identify its role without opening the schema.

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 gives concrete triggering conditions: "after list_projects when the user wants to continue work on an existing project, or when the connector starts without an active project." It does not explicitly name the when-not case (e.g., creating a new project instead), but the usage context is clearer than most siblings'.

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

All ChatCut toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources