Skip to main content
Glama

Save Video Quality Feedback

video_feedback_save
DestructiveIdempotent

Save the user's 1-5 rating and optional quality category/comment against one completed playable video export. Replaces that user's previous feedback for this export; does not change accepted clips or defaults. Requires the feedback storage migration to be installed.

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": {
      "workspaceId": "<workspaceId>",
      "idempotencyKey": "<idempotencyKey>",
      "exportId": "<exportId>",
      "rating": "<rating>",
      "category": "<category>",
      "comment": "<comment>"
    },
    "name": "video_feedback_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingYes
commentYes
categoryYes
exportIdYesUUID string.
workspaceIdYes
idempotencyKeyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / category / default
      Added value: +null
    • addedInput schema / properties / comment / default
      Added value: +""
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description earns credit by explaining exactly what is destroyed ('replaces that user's previous feedback for this export') and what is untouched (accepted clips, defaults). It also discloses an operational prerequisite (the feedback storage migration). It stops short of covering error behavior or permission requirements, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and scope, followed by overwrite semantics and the prerequisite. No redundant restatement of the name or title; every clause carries information an agent needs before calling.

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?

An output schema exists, so return values need no explanation, and the description covers the destructive overwrite semantics and prerequisite that the annotations alone only hint at. The remaining gap is the required idempotencyKey and workspace scoping, neither of which is described anywhere.

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 only 17%, so the description has to carry the load. It adds real meaning for rating (1-5 scale), category/comment (optional), and exportId (one completed playable export), but workspaceId and idempotencyKey — both required — are never explained in either place, which matters given the idempotent hint.

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 (save), a specific resource (the user's 1-5 rating plus optional category/comment), and a tightly scoped target (one completed playable video export). No sibling tool covers feedback capture, so there is nothing to confuse it with, and the 'completed playable video export' qualifier rules out calling it on in-progress exports.

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 the precondition for use (a completed playable export) and explicit scope exclusions ('does not change accepted clips or defaults'), plus an installation prerequisite. What it lacks is any routing guidance toward an alternative path, but no sibling offers a competing feedback operation, so the practical gap is small.

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.

Resources