Skip to main content
Glama

kelpo_select_editing_sources

Select up to 12 completed videos owned by the authenticated account, in order. Uses the editing version. No rendering or charge. Arguments: {"path": {"id": ""}, "body": {"version": 3, "job_ids": []}}

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": {
      "path": "<path>",
      "body": "<body>"
    },
    "name": "kelpo_select_editing_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / type
      Added value: +"object"
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare non-readOnly, non-destructive, non-idempotent; the description usefully adds that no rendering or charge is incurred, which the annotations do not convey. However it does not say whether this replaces a prior selection, whether order is persisted, or what happens if more than 12 ids are supplied beyond the schema's maxItems.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The first two sentences are front-loaded and useful, but the trailing 'Arguments: {…}' JSON dump repeats what the schema already defines and contains no explanatory text, so it spends space without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-mutating tool with a nested object, two required params, zero schema descriptions and no output schema, the description leaves too much unexplained: no return behavior, no prerequisites, no follow-on step guidance (e.g., that kelpo_start_editing or kelpo_preview_editing typically follows), and no error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, and it largely doesn't: it re-serializes an example body/path rather than explaining what 'version' means (editing version identifier), what path.id refers to, or that job_ids are video job identifiers. The only genuine semantic addition is 'in order', which hints that array order matters.

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?

States a specific verb (select) and resource (completed videos / editing sources), with scope (up to 12, owned by the authenticated account, ordered). It distinguishes itself reasonably from siblings like kelpo_start_editing and kelpo_get_editing, though it never names an alternative 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?

'Uses the editing version' and 'No rendering or charge' imply this is a cheap preparatory step before editing, but the description never says when to call this versus kelpo_start_editing, kelpo_get_editing, or kelpo_preview_editing, nor what prerequisites (an existing editing session?) must be met.

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