AwesomeVideo

Save or delete glossary terms

update_glossary

DestructiveIdempotent

Free, needs a key. Changes the saved transcription glossary that every later transcription of this account uses (brand names, people, slang spellings, doNotTranslate terms). action save: entries [{term, aliases?, doNotTranslate?}] merged by term (mode merge, default) or replacing the whole glossary (mode replace). action delete: remove terms, or all:true to clear it. Returns the glossary after the change. Read it with get_glossary.

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": "update_glossary"
  }
}

Input Schema

Name	Required	Description
`all`	No	true = delete the whole glossary. Pass this or terms.
`mode`	No	'merge' (default) adds or updates by term; 'replace' overwrites the whole glossary.
`terms`	No	Terms to remove (exact term text). Pass this or all.
`action`	Yes	save (entries) or delete (terms or all).
`entries`	No	Terms to save: [{term, aliases?: string[] (max 10), doNotTranslate?: boolean}], up to 200 terms in total.

Output Schema

Name	Required	Description
`total`	No	Total number of items (paginated lists).
`result`	No	The value, when the tool returns something other than an object.
`hasMore`	No	true when more items are available (paginated lists).
`nextCursor`	No	Pass as cursor for the next page (paginated lists).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, it explains the account-wide impact on every later transcription, the authentication requirement ('needs a key'), the merge-by-term default, the destructive replace/clear behaviors, and that the glossary is returned after the change.

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 dense but front-loaded with the key operational facts: auth, scope, action semantics, and the read alternative. Every sentence adds practical information without padding.

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?

An output schema exists, so return values need not be fully explained, and the description still notes that the updated glossary is returned. It covers authentication, global impact, both actions, mode behavior, deletion paths, and the sibling read tool.

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 parameter basics are already documented. The description still adds useful cross-parameter context: entries apply to save, terms/all apply to delete, merge updates by term, and replace overwrites the entire glossary.

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: changing the saved transcription glossary, with distinct save and delete actions. It also names the sibling read tool, get_glossary, so an agent can immediately distinguish mutation from retrieval.

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

Usage Guidelines5/5

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

It explicitly maps actions to use cases: save with entries, delete with terms or all:true, and merge versus replace modes. The instruction to read with get_glossary provides an explicit alternative for non-mutating access.

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

All AwesomeVideo tools Inspect

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

Need Help?