Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Fetch url

fetch_url

Downloads media from a supplied direct-file or supported media-page URL into the project. Media kind is detected automatically or explicitly selected, including audio-only extraction. Downloading an asset does not place it on the timeline.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
as_kindNo
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. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false, so the agent knows this tool makes external calls, may not be safe to repeat, and has limited side effects. The description usefully adds that media kind is auto-detected or can be overridden and that the asset is not placed on the timeline, but it does not say what constitutes a "supported" media page, what happens when a download fails or is repeated, or whether the asset is persisted in the project library.

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?

Three short sentences, front-loaded and with no filler. The key side effect ('does not place it on the timeline') is stated up front, and it would be even stronger if the follow-up tool had been named in the same breath.

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

Completeness3/5

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

For a network-dependent ingestion tool with no output schema, the description never says what the call returns (an asset id, a job handle, or both), so the agent cannot know how to reference the fetched media later. The concept of a 'project' target is at least addressed by the schema's project_id note.

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 33%: only project_id is documented. The description partially compensates by saying media kind is auto-detected or explicitly selected, which explains as_kind conceptually and implies it is optional (enum values clip, music, image are never named). It also broadens 'url' to mean direct-file or media-page URLs, adding real meaning. Still, the mapping between 'audio-only extraction' and the enum has to be guessed.

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 and resource: it downloads media from a direct-file or supported media-page URL into the project, and it can extract audio only. The purpose is clear, but the description never distinguishes this tool from the near-identical sibling download_url or from insert_media, so an agent must infer which one to call.

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?

The line "Downloading an asset does not place it on the timeline" implies the follow-up flow — fetch first, then place the asset with an insert tool — but the description never says so explicitly. It also names no alternative for URL ingestion despite having download_url and add_stock_media as siblings; the choice is left to inference.

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