Skip to main content
Glama

Файлы аккаунта

manage_workspace_files
Destructive

Файлы аккаунта: чем занято место и чистка. overview — сколько занято, сколько разрешает тариф и разбивка по опросам. list — сами файлы с фильтрами по опросу, виду медиа, хранилищу и владельцу, с поиском и сортировкой. delete — удаление выбранных файлов или всех файлов перечисленных опросов. Удаление необратимо: файл респондента приложен к его ответу, и после удаления в ответе останется ссылка в никуда, поэтому нужно подтверждение. Загрузить файл через ассистента нельзя, скачать архивом — тоже. Скрытые из-за нехватки места файлы — в get_workspace_hidden_files.

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": {
      "workspace_id": "<workspace_id>",
      "action": "<action>"
    },
    "name": "manage_workspace_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoСтраница, с 1.
ownerNoЧьи файлы: owner — загруженные автором в опрос, respondent — присланные респондентами, both — и те, и другие (для delete).
actionYesЧто сделать: overview — сводка по месту, list — список файлов, delete — удалить.
searchNoПоиск по имени файла.
quiz_idNoПоказать файлы только этого опроса. Для list.
sort_byNoСортировка: quiz_id, size, created_at или storage.
storageNoГде лежит файл: default — наше хранилище, s3 или yandex_disk — своё хранилище аккаунта.
file_idsNoID конкретных файлов из list. Без них нужен delete_all.
per_pageNoФайлов на странице, 1–200. По умолчанию 30.
quiz_idsNoОпросы, в которых удаляем файлы. Обязательно для delete.
delete_allNoУдалить все файлы перечисленных опросов, а не выбранные. Идёт очередью, поэтому число удалённых в ответе не приходит.
file_uuidsNoUUID файлов респондентов из list. У них нет числового id — только uuid, поэтому удалять их надо этим полем.
media_typeNoВид медиа: image, video или audio.
workspace_idYesID аккаунта из workspace://list.
confirm_deleteNoОбязательное подтверждение удаления: восстановить файлы нечем.
sort_directionNoНаправление сортировки: asc или desc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and non-idempotent, but the description adds the consequence that annotations cannot express: deletion is irreversible, a respondent's file is attached to their answer, and removing it leaves a dangling link in the answer. It also warns that delete_all runs as a queue and therefore does not report a deleted count — behavior no annotation or schema field conveys.

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?

The text is front-loaded by action in a single dense paragraph, with the destructive warning and the sibling pointer placed last where they matter most. It is somewhat long and partly echoes schema text, but every sentence carries operational information rather than filler.

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?

For a 16-parameter, three-mode destructive tool with no output schema, the description covers what overview returns, what delete destroys, and what the tool cannot do. Remaining gaps are minor: it does not state what a successful delete response contains (beyond the queued-delete caveat) or any permission/ownership prerequisites.

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 100%, so all 16 parameters already carry their own descriptions, including the owner, storage, quiz_ids/file_ids/file_uuids and confirm_delete semantics. The description restates the filter axes (quiz, media type, storage, owner) at a high level but adds little syntax or edge-case meaning beyond what the schema already documents, so the baseline 3 applies.

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?

The description names a specific resource (account files) and enumerates its three concrete modes: overview (space used vs. plan limit plus per-quiz breakdown), list (files with filters, search, sorting) and delete. An agent can distinguish this from get_workspace_hidden_files or the quiz-report file tools 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?

Each action is tied to a situation, delete is gated on explicit confirmation, and the description states two negative cases (you cannot upload a file via the assistant or download an archive) plus routes hidden files to get_workspace_hidden_files. That is explicit when-to-use, when-not-to-use and an alternative, which is the top of the scale.

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