Skip to main content
Glama
Sign In

ChatCut

by io.chatcut
OverviewDiscussionsAdmin

edit_project

Update project-level settings or speakers.

Actions:

  • update: change project name/description.

  • speaker-create / speaker-update / speaker-delete: manage the speaker list used by transcripts.

Canvas size and aspect ratio are per-timeline state — change them with manage_timelines action=update.

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": {
      "action": "<action>"
    },
    "name": "edit_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSpeaker ID (for speaker ops)
jsonNoJSON payload
actionYesupdate, speaker-create, speaker-update, or speaker-delete
projectIdNoProject for this call (full ID or unambiguous prefix). Explicit-timeline calls never change the target of later calls; legacy project selection applies otherwise.
timelineIdNo

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/5.0
Behavior3/5

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

The per-timeline state note is genuinely useful context beyond the annotations, and annotations already declare non-read-only, non-idempotent behavior. However, the description advertises a speaker-delete action without saying whether removal orphans speaker references in existing transcripts or is reversible — notable given destructiveHint=false on a tool that exposes a delete action. The json payload's expected shape is also undisclosed.

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?

Three short blocks: a one-line purpose, a bulleted action list, and a single routing sentence. Front-loaded, zero filler, and the scoping caveat is placed after the primary behavior where it belongs.

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?

For a five-parameter multi-action mutation tool with no output schema, the description covers purpose, action semantics, and sibling routing adequately. The remaining gaps — the json payload contract and side effects of speaker-delete on existing transcripts — are real but narrow.

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 80%, so the schema already documents id, projectId, and action. The description adds meaning by mapping each action name to an outcome, which the schema's bare enumeration does not. It adds nothing about the `json` payload contents or the empty-description `timelineId`, leaving the highest-risk parameter opaque.

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 names a specific verb and resource ("Update project-level settings or speakers") and then enumerates the four discrete actions. It also carves out an explicit non-scope ("Canvas size and aspect ratio are per-timeline state"), which separates it cleanly from manage_timelines and create_project.

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 states what each action does and gives one explicit routing rule with the alternative named (canvas/aspect ratio → manage_timelines action=update). It does not address overlap with nearby siblings such as manage_character, manage_voice, or read_project, so an agent must still infer when a speaker operation belongs here rather than in a character/voice tool.

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