Skip to main content
Glama

Выключить или включить публичную ссылку

set_share_link_active
Destructive

Выключает или включает публичную ссылку на сводку, отчёт или ответы. Выключенная ссылка перестаёт открываться: по ней больше не видны результаты. Ссылка не удаляется — её можно включить обратно. У ссылки отчёта или ответов меняет и показ аудио- и видеоответов (media_responses). Нужно передать is_active, media_responses или оба. uuid берётся из get_share_links.

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": {
      "quiz_id": "<quiz_id>",
      "section": "<section>",
      "uuid": "<uuid>"
    },
    "name": "set_share_link_active"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesuuid ссылки из get_share_links.
quiz_idYesID опроса.
sectionYesРаздел ссылки: summary — сводка, report — отчёт, answers — ответы.
is_activeNofalse — выключить ссылку, true — включить обратно. Не передан — не меняется.
media_responsesNoТолько report и answers: что показывать по ссылке у аудио- и видеоответов. Непереданный флаг не меняется. Снятие флага сразу закрывает уже выданные по ссылке записи.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / is_active / description
      Previous value: -"false — выключить ссылку, true — включить обратно."New value: +"false — выключить ссылку, true — включить обратно. Не передан — не меняется."
    • addedInput schema / properties / media_responses
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Только report и answers: что показывать по ссылке у аудио- и видеоответов. Непереданный флаг не меняется. Снятие флага сразу закрывает уже выданные по ссылке записи.",
      +  "minProperties": 1,
      +  "properties": {
      +    "include_media": {
      +      "description": "«Записи»: метаданные записи и прослушивание или скачивание по ссылке.",
      +      "type": "boolean"
      +    },
      +    "include_transcripts": {
      +      "description": "«Текстовые ответы и расшифровки»: текст вместо записи и расшифровки.",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "quiz_id",
      -  "section",
      -  "uuid",
      -  "is_active"
      -]New value: +[
      +  "quiz_id",
      +  "section",
      +  "uuid"
      +]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description usefully tempers that by explaining the operation is reversible: the link is not deleted and can be re-enabled, while a disabled link stops resolving for recipients. It also warns that clearing a media flag immediately revokes recordings already handed out via the link. It does not cover permission requirements, which is the remaining gap.

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?

Five short sentences, front-loaded with the core action and consequence before the parameter mechanics and the uuid prerequisite. Minor waste from repeating the schema's own statement that uuid comes from get_share_links, but nothing is padded or buried.

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 5-parameter mutation with a nested object, full schema coverage and no output schema, the description covers the action, its reversibility, the side effect on existing links, and the mutual-requirement constraint. The only material omission is authorization or scope requirements for who may flip a public link.

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 description coverage is 100%, so the schema already documents every field, including the enum for section and the nested media_responses flags; baseline is therefore 3. The description does add one genuinely new rule not present in the schema — that is_active, media_responses, or both must be passed — but otherwise largely restates schema content such as uuid provenance and the report/answers restriction.

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 opening sentence names a specific verb pair (enable/disable) and the exact resource (public share link) plus its three scopes (summary, report, answers). An agent can tell this is a toggle on an existing link rather than a creation tool, and the reference to get_share_links anchors it against the share_* siblings.

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?

It establishes the prerequisite workflow (uuid comes from get_share_links) and states the call constraint that at least one of is_active or media_responses must be supplied, which is clear usage context. It stops short of naming an alternative tool or saying when not to use this one, so it falls short of a 5.

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