Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Get words

get_words
Read-only

Returns word-level timestamps for a source-time range of the main recording or a specified uploaded clip. Responses contain at most 400 words with pagination information. Asset-specific timestamps belong to that clip.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
asset_keyNo
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."
  2. Changed1 schema field changed
    • addedInput schema / properties / asset_key
      Added value: +{
+  "type": "string"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish this is a read-only, non-destructive call, so the description is free to add the details that matter: a hard cap of 400 words per response with pagination information, and that ranges are expressed in source time and that clip timestamps are scoped to the clip. It does not explain how to page past the 400-word cap, which leaves a real gap.

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 operation and resource, then the response-size constraint, then the clip-scoping caveat. No filler or repetition of the title.

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?

With no output schema, the description takes on return-value explanation and does so reasonably (word-level timestamps plus pagination information). The main omission is whether start/end are optional and how pagination is actually advanced, given no cursor parameter exists in the schema.

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 only 25% (only project_id is documented), so the description must compensate. It does add meaning for start/end by calling them a 'source-time range' and for asset_key by tying it to a 'specified uploaded clip', but units, defaults, and whether the range is optional are left unstated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Returns word-level timestamps') and scopes it to 'the main recording or a specified uploaded clip'. That is enough to separate it from transcript- or syllable-level siblings, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: word-level timing as opposed to transcript text, and the 'asset-specific timestamps belong to that clip' note hints at choosing between the main recording and a clip. There is no explicit when-to-use / when-not-to-use statement or named alternative such as get_transcript.

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

All Valmera — AI Video Editor 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