Skip to main content
Glama

label

Manage source labels in a notebook: auto-categorize, create, rename, assign emoji, move sources, or delete labels. Organize sources into thematic groups.

Instructions

Manage source labels in a notebook. Unified tool for all label operations.

Labels let you organize sources into thematic categories. Requires 5+ sources for auto-labeling. Sources can belong to multiple labels simultaneously.

Supports: auto, list, reorganize, create, rename, set_emoji, move_source, delete

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoLabel display name (required for create and rename)
emojiNoEmoji character for set_emoji (e.g. "📊"), or "" to clear
actionYesOperation to perform: - auto: AI auto-labels all sources into thematic categories - list: List current labels (triggers AI if none exist) - reorganize: Force AI re-categorization (requires confirm=True unless unlabeled_only=True) - create: Create a new empty label (requires name) - rename: Rename a label (requires label_id, name) - set_emoji: Set or clear emoji on a label (requires label_id, emoji) - move_source: Assign a source to a label (requires label_id, source_id) - delete: Delete label(s) permanently (requires label_id or label_ids, confirm=True)
confirmNoMust be True for delete action and for reorganize with unlabeled_only=False
label_idNoLabel UUID (required for rename, set_emoji, move_source, delete)
label_idsNoList of label UUIDs for batch delete (alternative to label_id)
source_idNoSource UUID to assign (required for move_source)
notebook_idYesNotebook UUID
unlabeled_onlyNoFor reorganize: if True, only label sources not yet in any label. If False (default), replaces ALL existing labels from scratch (requires confirm=True).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations provided, so description carries full burden. It mentions 'Requires 5+ sources for auto-labeling' and that sources can belong to multiple labels, but fails to disclose behavioral traits of actions like reorganize (which can be destructive) or delete (requires confirmation).

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?

Description is short (4 sentences) and front-loaded with purpose. However, the list of actions is redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 parameters, multiple actions) and lack of annotations, the description is insufficient. It does not explain when to use each action or provide context beyond the schema, despite having an output schema.

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 baseline is 3. The description lists supported actions but does not add meaning beyond what the schema already provides for each parameter.

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 clearly states 'Manage source labels in a notebook' and lists supported operations, making the tool's purpose evident. However, it does not differentiate from the sibling 'tag' tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'tag'. Only mentions a condition for auto-labeling (requires 5+ sources), but no explicit when-to-use or when-not-to-use advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlexanderKast/cast-notebooklm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server