Skip to main content
Glama

cancel_answer

Stops an in-flight streaming answer in NotebookLM, acting as the UI Stop control. Defaults to the most recent conversation.

Instructions

Stop a notebook’s in-flight answer — the UI’s “Stop” on a streaming reply. RPC-backed. Fire-and-forget: the server does not confirm, so cancelled: true means the stop was sent, not that a turn was running. Defaults to the most recent conversation.

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": "cancel_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
notebook_idNoNotebook UUID (alternative to notebook_url).
notebook_urlNoNotebookLM notebook URL.
conversation_idNoA specific conversation. Defaults to the most recent one.

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool payload on success. The exact shape depends on the tool.
errorNoHuman-readable error message, present only when success is false.
successYesWhether the tool call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.9.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the RPC backing, the fire-and-forget contract, and — critically — that `cancelled: true` only means the stop was sent, not that a turn was running. It does not cover error behavior or idempotency when nothing is streaming, keeping it out of the top band.

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?

Three short sentences, each load-bearing: identity first, mechanism second, return-value caveat third. No repetition or filler, and the most easily misunderstood fact (the meaning of the success flag) is placed prominently.

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?

Output schema exists, so return values needn't be explained, and the description still clarifies the one return semantic that matters. Three optional params at full coverage mean little is missing; only failure/no-op behavior is unaddressed for an unannotated RPC tool.

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 100% and the description's only parameter-level detail is the default-to-most-recent conversation behavior for conversation_id, which the schema already states. It adds no new semantics about notebook_id vs notebook_url or conversation scoping beyond what structured fields provide.

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?

Names a specific verb and resource ("Stop a notebook's in-flight answer") and anchors it to a concrete UI affordance ("the UI's 'Stop' on a streaming reply"), which distinguishes it from cancel_research and the auth/content siblings. An agent can identify exactly which operation this performs without further reading.

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?

Makes the triggering condition clear (an answer is streaming and should be halted) and states the scoping default to the most recent conversation. It stops short of naming an alternative tool or saying what to do when nothing is in flight, so the when-not guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.