Skip to main content
Glama

Valmera — agentic AI video editor

by io.valmera
OverviewDiscussionsAdmin

Read an editing skill

read_skill
Read-only

PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Load a focused editing playbook (captions, zooms, audio, transitions, ...) into this turn. The SKILLS list in your instructions names them. Read the matching skill before your first edit of that kind — batch it with your other reading calls. Pass section to retrieve only the decision, evidence, pattern, failure, verification, or repair material needed now.

Input Schema

NameRequiredDescriptionDefault
nameYes
sectionNo
project_idYesRequired immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / enum
      Previous value: -[
-  "acquisition",
-  "audio",
-  "beats-emphasis",
-  "broll-inserts",
-  "captions",
-  "compositing",
-  "creative-direction",
-  "cutting",
-  "devices",
-  "effects-grades",
-  "elements",
-  "finishing",
-  "formats",
-  "generate-fetch",
-  "hooks-retention",
-  "layouts",
-  "montage",
-  "motion-design",
-  "music",
-  "occlusion",
-  "premium-composition",
-  "punctuation",
-  "reframe-aspect",
-  "review",
-  "rhythm",
-  "screen-takeover",
-  "short-form-direction",
-  "structure",
-  "subject-fx",
-  "text-graphics",
-  "tracking",
-  "transitions",
-  "type-fx",
-  "type-in-world",
-  "typesetting",
-  "world",
-  "zooms"
-]New value: +[
+  "acquisition",
+  "audio",
+  "beats-emphasis",
+  "broll-director",
+  "broll-inserts",
+  "captions",
+  "compositing",
+  "creative-direction",
+  "critic",
+  "cutting",
+  "delivery",
+  "depth-time",
+  "devices",
+  "effects-grades",
+  "elements",
+  "explainers",
+  "finishing",
+  "formats",
+  "generate-fetch",
+  "hooks-retention",
+  "layouts",
+  "montage",
+  "motion-design",
+  "music",
+  "occlusion",
+  "premium-composition",
+  "punctuation",
+  "reframe-aspect",
+  "review",
+  "rhythm",
+  "screen-takeover",
+  "short-form-direction",
+  "structure",
+  "subject-fx",
+  "text-graphics",
+  "tracking",
+  "transitions",
+  "type-fx",
+  "type-in-world",
+  "typesetting",
+  "world",
+  "zooms"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / name / enum
      Previous value: -[
-  "audio",
-  "beats-emphasis",
-  "broll-inserts",
-  "captions",
-  "compositing",
-  "creative-direction",
-  "cutting",
-  "devices",
-  "effects-grades",
-  "finishing",
-  "formats",
-  "generate-fetch",
-  "hooks-retention",
-  "montage",
-  "motion-design",
-  "music",
-  "premium-composition",
-  "punctuation",
-  "reframe-aspect",
-  "review",
-  "rhythm",
-  "screen-takeover",
-  "short-form-direction",
-  "structure",
-  "subject-fx",
-  "text-graphics",
-  "transitions",
-  "type-fx",
-  "typesetting",
-  "zooms"
-]New value: +[
+  "acquisition",
+  "audio",
+  "beats-emphasis",
+  "broll-inserts",
+  "captions",
+  "compositing",
+  "creative-direction",
+  "cutting",
+  "devices",
+  "effects-grades",
+  "elements",
+  "finishing",
+  "formats",
+  "generate-fetch",
+  "hooks-retention",
+  "layouts",
+  "montage",
+  "motion-design",
+  "music",
+  "occlusion",
+  "premium-composition",
+  "punctuation",
+  "reframe-aspect",
+  "review",
+  "rhythm",
+  "screen-takeover",
+  "short-form-direction",
+  "structure",
+  "subject-fx",
+  "text-graphics",
+  "tracking",
+  "transitions",
+  "type-fx",
+  "type-in-world",
+  "typesetting",
+  "world",
+  "zooms"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / name / enum
      Previous value: -[
-  "audio",
-  "beats-emphasis",
-  "broll-inserts",
-  "captions",
-  "compositing",
-  "cutting",
-  "devices",
-  "effects-grades",
-  "finishing",
-  "formats",
-  "generate-fetch",
-  "hooks-retention",
-  "motion-design",
-  "music",
-  "premium-composition",
-  "punctuation",
-  "reframe-aspect",
-  "review",
-  "screen-takeover",
-  "short-form-direction",
-  "subject-fx",
-  "text-graphics",
-  "transitions",
-  "zooms"
-]New value: +[
+  "audio",
+  "beats-emphasis",
+  "broll-inserts",
+  "captions",
+  "compositing",
+  "creative-direction",
+  "cutting",
+  "devices",
+  "effects-grades",
+  "finishing",
+  "formats",
+  "generate-fetch",
+  "hooks-retention",
+  "montage",
+  "motion-design",
+  "music",
+  "premium-composition",
+  "punctuation",
+  "reframe-aspect",
+  "review",
+  "rhythm",
+  "screen-takeover",
+  "short-form-direction",
+  "structure",
+  "subject-fx",
+  "text-graphics",
+  "transitions",
+  "type-fx",
+  "typesetting",
+  "zooms"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / name / enum
      Previous value: -[
-  "audio",
-  "beats-emphasis",
-  "broll-inserts",
-  "captions",
-  "cutting",
-  "effects-grades",
-  "formats",
-  "generate-fetch",
-  "hooks-retention",
-  "motion-design",
-  "music",
-  "premium-composition",
-  "reframe-aspect",
-  "review",
-  "screen-takeover",
-  "short-form-direction",
-  "text-graphics",
-  "transitions",
-  "zooms"
-]New value: +[
+  "audio",
+  "beats-emphasis",
+  "broll-inserts",
+  "captions",
+  "compositing",
+  "cutting",
+  "devices",
+  "effects-grades",
+  "finishing",
+  "formats",
+  "generate-fetch",
+  "hooks-retention",
+  "motion-design",
+  "music",
+  "premium-composition",
+  "punctuation",
+  "reframe-aspect",
+  "review",
+  "screen-takeover",
+  "short-form-direction",
+  "subject-fx",
+  "text-graphics",
+  "transitions",
+  "zooms"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / name / enum
      Previous value: -[
-  "audio",
-  "beats-emphasis",
-  "broll-inserts",
-  "captions",
-  "cutting",
-  "effects-grades",
-  "formats",
-  "generate-fetch",
-  "hooks-retention",
-  "music",
-  "premium-composition",
-  "reframe-aspect",
-  "review",
-  "screen-takeover",
-  "short-form-direction",
-  "text-graphics",
-  "transitions",
-  "zooms"
-]New value: +[
+  "audio",
+  "beats-emphasis",
+  "broll-inserts",
+  "captions",
+  "cutting",
+  "effects-grades",
+  "formats",
+  "generate-fetch",
+  "hooks-retention",
+  "motion-design",
+  "music",
+  "premium-composition",
+  "reframe-aspect",
+  "review",
+  "screen-takeover",
+  "short-form-direction",
+  "text-graphics",
+  "transitions",
+  "zooms"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / name / enum
      Previous value: -[
-  "audio",
-  "beats-emphasis",
-  "broll-inserts",
-  "captions",
-  "cutting",
-  "effects-grades",
-  "formats",
-  "generate-fetch",
-  "hooks-retention",
-  "music",
-  "reframe-aspect",
-  "review",
-  "screen-takeover",
-  "short-form-direction",
-  "text-graphics",
-  "transitions",
-  "zooms"
-]New value: +[
+  "audio",
+  "beats-emphasis",
+  "broll-inserts",
+  "captions",
+  "cutting",
+  "effects-grades",
+  "formats",
+  "generate-fetch",
+  "hooks-retention",
+  "music",
+  "premium-composition",
+  "reframe-aspect",
+  "review",
+  "screen-takeover",
+  "short-form-direction",
+  "text-graphics",
+  "transitions",
+  "zooms"
+]
  7. Changed1 schema field changed
    • addedInput schema / properties / name / enum
      Added value: +[
+  "audio",
+  "beats-emphasis",
+  "broll-inserts",
+  "captions",
+  "cutting",
+  "effects-grades",
+  "formats",
+  "generate-fetch",
+  "hooks-retention",
+  "music",
+  "reframe-aspect",
+  "review",
+  "screen-takeover",
+  "short-form-direction",
+  "text-graphics",
+  "transitions",
+  "zooms"
+]
  8. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds meaningful context beyond them: the project-scoping constraint, that the result echoes project identity, and that `section` narrows the payload. It does not discuss rate limits or result size, keeping it just short of 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?

Front-loaded with the critical PROJECT-SCOPED constraint, then purpose, then usage. Dense but each sentence carries an instruction; slightly long but nothing is redundant.

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?

No output schema, but the description discloses the return includes project identity. Combined with the schema enums and annotations, an agent has enough to call it correctly; the only minor gap is that section/name contents are only described in outline.

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 only 33%, so the description must compensate, and it does: it explains that `section` retrieves only the specific material needed now and that `name` should come from the SKILLS list in the agent's instructions. It adds intent beyond the enum values themselves, though exact semantics of each section remain inferred.

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?

States a specific verb and resource ('Load a focused editing playbook... into this turn') and clarifies scope ('PROJECT-SCOPED: this call acts only on the explicit project_id'). No sibling tool performs this read, so the agent can identify it unambiguously from the description alone.

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?

Gives explicit timing: 'Read the matching skill before your first edit of that kind' and adds a batching instruction. It also tells the agent to use the SKILLS list in its instructions for valid names. It does not name a fallback/alternative tool, but the when-to-use context is clear.

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

All Valmera — agentic 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