Qué hace
Get one task in full: notes, metadata, subtasks, any calendar events it's tied to, and the activity feed (comments + status history, each entry naming who wrote it). Call before working a task to load context the human left.
CONTEXT BUDGET: the activity feed returns the NEWEST 50 entries by default. Use limit (0–500) to change that, and include to ask for only the sections you need. Whenever anything is left out, the response carries context_summary saying exactly what — how many older entries exist and which sections you didn't request — so a short payload is never mistaken for a complete history. If it is absent, you have everything. When it says entries were omitted, reach for search_activity rather than assuming; do not infer that a task has no earlier history from a feed that was windowed.
It also resolves all three tiers of the human's standing instructions to you, so you read them in the same call that loads the work: workspace_brief (everything in this workspace), project_brief (everything in this project), and the task's own notes_for_agent. PRECEDENCE: workspace → project → task, most specific last. They are additive context, not a chain where one replaces another — read all three. Where two genuinely conflict, the narrower one is a more recent decision about narrower ground, so it wins: the task's note beats the project brief, which beats the workspace brief. All three are one-way, from the human to you; reply with comment_on_task, or propose new wording for the project or task brief with propose_brief_edit (ask_decision for the workspace one). A task that was sent back and has no brief proposal off it yet carries a one-line brief_hint saying so.
Parámetros
| Nombre | Tipo | Obligatorio | Descripción |
|---|---|---|---|
id | string | Obligatorio | |
include | string[] | Opcional | Which optional sections to load. Omit for all of them. The task itself and all three standing briefs are always returned — they are the human's instructions to you, not an optional section. Valores permitidos subtasksblockerstagsactivityrunsdecisionscalendar |
limit | integer | Opcional | Newest activity entries to return (default 50). 0 returns the counts without the entries.
|
Anotaciones
Las pistas que el servidor envía con esta herramienta. Un cliente las lee para decidir si te pregunta antes de llamarla.
- Solo lectura
readOnlyHint: true - No cambia nada.
- Destructiva
destructiveHint: false - Solo agrega o lee; no quita ni sobrescribe nada de lo que ya existe.
- Idempotente
idempotentHint: — - No aplica: la herramienta no cambia nada.
- Mundo abierto
openWorldHint: false - Solo toca tu propia cuenta de Done.
Qué tokens pueden llamarla
Una conexión hecha con OAuth tiene acceso completo. Un token de Ajustes → Acceso de agentes → Tokens de MCP adicionales se puede acotar, y un token acotado nunca ve más allá de su proyecto o espacio de trabajo.
- Acceso completoPermitido
- Token de solo lecturaPermitido
- Token de un proyectoPermitido
- Token de un espacio de trabajoPermitido
Pruébala
Con Done conectado, pídele a tu asistente algo como:
“Abre la tarea de la lista de lanzamiento y lee todo lo que dejé en ella.”
Conecta Done a tu asistente
Un endpoint MCP por cuenta, con OAuth o con un token. Configuración paso a paso para cada cliente: