Skip to main content
Glama

create_clip

Destructive

Guarda una página web como clip, igual que pegar una URL en la app: el servidor baja la página, la limpia y la IA la entiende (resumen y puntos clave aparecen en unos segundos, vía get_clip). Reclipear la misma URL NO duplica: actualiza el clip existente.

Para un texto que no es una página (una nota, una cita) no uses clips: es un
documento (create_document) o una línea del Diario.

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>"
    },
    "name": "create_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL http(s) de la página
noteNoUna nota propia sobre por qué se guardó
titleNoTítulo; si falta, el de la página
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 bajo el que cuelga el clip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by describing the server pipeline (download, clean, AI understanding), the asynchronous timing of results, and the de-duplication rule on re-clipping. The dedupe wording ('actualiza el clip existente') sits in mild tension with idempotentHint=false and the destructiveHint=true overwrite is only implied, but it is not a genuine contradiction and the added context is substantial.

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-loads the core action, then the async behavior, then the dedupe rule, then the exclusion case. Every sentence carries information, though the parenthetical about summary timing could be trimmed slightly without loss.

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?

With no output schema, the description still tells the agent what becomes available and where (summary and key points via get_clip), plus how repeat calls behave. Nothing needed to call this correctly on a five-parameter, open-world write tool is missing.

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 all five parameters (url, note, title, workspace_id, parent_document_id) are already documented in the schema. The description adds no per-parameter meaning beyond confirming that the input is a URL, 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?

States a specific verb and resource ('Guarda una página web como clip') and immediately anchors it with a concrete analogy ('igual que pegar una URL en la app'). It also distinguishes itself from document creation, so an agent can tell it apart from create_document without opening either 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 an explicit exclusion: text that is not a page (a note, a quote) should go to create_document or the Diario line instead. It also names get_clip as the follow-up call for retrieving the summary, so both the when and the when-not are covered.

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