Skip to main content
Glama

update_clip

DestructiveIdempotent

Edita un clip: título, nota propia, resumen o el documento del que cuelga (null lo suelta). Sólo se toca lo que se manda.

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": {
      "clip_id": "<clip_id>"
    },
    "name": "update_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
titleNo
clip_idYesID del clip (de get_clips)
summaryNo
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
parent_document_idNoDocumento padre, o null para soltarlo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real behavior beyond that: partial-update semantics ('sólo se toca lo que se manda') and the fact that passing null for the parent detaches the clip, which explains the destructive edge case. It still omits permission requirements and what happens on an invalid clip_id.

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

Conciseness5/5

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

Two short sentences, front-loaded with the verb and the affected fields, and the partial-update rule closes it out. No filler or redundant restatement of the tool name.

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 six-parameter mutation tool with no output schema and annotations covering the safety profile, the description covers what can be changed, the partial-update contract, and the null-detach case. Remaining gaps (authentication/ownership requirements, response shape) are modest given the annotation coverage.

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 50%: clip_id, workspace_id and parent_document_id are documented in the schema. The description names the editable fields (title, note, summary, parent_document_id) but only repeats the null-detach behavior already stated in the schema's parent_document_id description. Fields like note ('nota propia') get a small disambiguation but workspace_id is only explained in the schema.

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?

The description gives a specific verb and resource ('Edita un clip') and enumerates the editable fields (título, nota propia, resumen, documento padre), which clearly separates it from create_clip/delete_clip/get_clip. It stops short of explicitly naming those siblings as alternatives.

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 clause 'Sólo se toca lo que se manda' tells the agent this is a partial update and that unspecified fields are left alone, which is implied guidance on how to call it. There is no explicit when-to-use versus create_clip or update_document, and no stated prerequisites.

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