Skip to main content
Glama

get_clips

Read-onlyIdempotent

Los clips del workspace: páginas guardadas desde el navegador y mails reenviados.

Un clip es material de AFUERA que alguien quiso conservar. Trae el texto
completo (`content_md`), y si ya pasó por la IA, `summary` y
`key_points`. `clip_mode` dice si se guardó la página entera o sólo una
selección.

Esta lista no trae el texto completo para no inundar la respuesta: pedí uno
puntual con get_clip.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 25)
queryNoBuscar en título, resumen o dominio
sourceNoDe dónde vino
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context: which fields a clip record carries (content_md, summary, key_points, clip_mode) and the deliberate omission of full text from list responses to avoid flooding the output — that is a response-shape trait an agent needs and no annotation provides.

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?

Three short paragraphs, front-loaded with the resource and scoped by the get_clip redirect at the end. The middle section defining clip fields is dense but earns its place by explaining clip_mode and the summary/key_points conditionality. Minor redundancy between the first and second paragraph on what a clip is.

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?

No output schema exists, so the description carries the burden of describing returned fields and does so (content_md, summary, key_points, clip_mode), including the conditional nature of summary/key_points. It also explains the pagination-ish limit default only via the schema. Complete enough for a simple read-list tool with full annotation and schema 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 description coverage is 100%, with each of the four params documented, including the enum values for source and the 'omit = ALL workspaces' semantics for workspace_id. The description only indirectly illuminates the source enum by saying clips come from browser pages and forwarded emails; it adds no syntax or format detail beyond the schema. 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 the resource and scope precisely ("Los clips del workspace") and defines what a clip is — pages saved from the browser and forwarded emails — so the agent knows exactly what domain this covers. It also explicitly separates itself from get_clip, which returns a single clip's full text.

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?

Gives an explicit routing rule: this tool returns the list without full text, and if you need one specific clip's body you should call get_clip. The condition that selects the alternative is stated. It does not address other plausible alternatives (e.g. get_all_files, get_document) but names alone don't establish those behaviors.

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