Skip to main content
Glama

Ask to connect a media folder

connect_media_folder

Asks the user to attach a folder of THEIR OWN source footage to the project — opens a dialog in Frapea with a 'Connect folder' button. Only a human can do this (browser security gesture): tell the user IN YOUR REPLY to click it, then call await_user_action with the returned actionId; on 'granted', get_media will list the folder's files. Use when get_media comes back empty and the user has footage somewhere on their disk. NEVER call it for files YOU made or fetched (download_web_video and the stock tools put theirs in the pool themselves). The project folder's media/ folder is scanned: any media file placed there joins the pool by itself (within a second, or when the user returns to the tab), with no dialog. reason is shown in the dialog word for word — say which footage you need and what you will do with it, so the user knows what to pick.

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": {
      "projectId": "<projectId>",
      "reason": "<reason>",
      "token": "<token>"
    },
    "name": "connect_media_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe session token `connect` returned. Pass it on every call — it says which browser to drive.
reasonYesOne or two sentences for the dialog, addressed to the user: which folder to pick and why — e.g. 'Pick the folder with your trip clips from Lisbon, so I can cut them into the reel you asked for.'
projectIdYesProject id from get_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare a non-read-only, non-destructive, non-idempotent local tool. The description adds far more: it requires a human browser gesture, must be surfaced to the user in the reply, hands off to await_user_action with a returned actionId, and resolves on 'granted' before get_media can list files. That is the full control flow an agent needs and cannot get from the annotations.

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 core action, then workflow, then exclusions, then the parameter note — a sensible order with no filler sentences. It runs long and leans on caps for emphasis, which is slightly noisy, but each sentence carries distinct information.

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?

For a three-parameter tool with no output schema, the description covers the trigger, the human-interaction requirement, the follow-up call, the success condition, and the bypass path. Nothing an agent needs in order to call it correctly is missing.

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 the baseline is 3, but the description adds real meaning beyond the schema for `reason`: it is displayed in the dialog word for word, so it must name the footage and the intended use. That is a non-obvious consequence (user-visible copy) rather than a restatement. `token` and `projectId` are left to the schema, which is acceptable given their coverage.

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 — asking the user to attach a folder of their own source footage — and immediately distinguishes it from tools that auto-populate the pool (download_web_video, stock tools, and the scanned media/ folder). An agent can identify the exact operation without opening the schema.

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?

Gives a positive trigger ('use when get_media comes back empty and the user has footage somewhere on their disk'), an explicit exclusion ('NEVER call it for files YOU made or fetched'), and a cheaper alternative (drop files into the project's media/ folder, which is auto-scanned). When-to-use, when-not-to-use, and alternatives are all present.

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