Skip to main content
Glama
jacob-bd

notebooklm-mcp

by jacob-bd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Studio Status

studio_status

Check studio content generation status and retrieve artifact URLs; rename artifacts when needed.

Instructions

Check studio content generation status and get URLs, or rename an artifact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum artifacts to return for status (1-100, default 20)
actionNoAction to perform: - status (default): List all artifacts with their status and URLs - rename: Rename an artifact (requires artifact_id and new_title) - list_types: List all supported artifact types with their optionsstatus
offsetNoNumber of artifacts to skip for status pagination
new_titleNoRequired for action="rename" - the new title for the artifact
artifact_idNoFor status, return only this artifact. Required for action="rename".
notebook_idYesNotebook UUID
include_detailsNoInclude prompts, source IDs, report content, and media details

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.11.2
    • addedInput schema / properties / action / description
      Added value: +"Action to perform:\n- status (default): List all artifacts with their status and URLs\n- rename: Rename an artifact (requires artifact_id and new_title)\n- list_types: List all supported artifact types with their options"
    • addedInput schema / properties / artifact_id / description
      Added value: +"For status, return only this artifact. Required for action=\"rename\"."
    • addedInput schema / properties / include_details / description
      Added value: +"Include prompts, source IDs, report content, and media details"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum artifacts to return for status (1-100, default 20)"
    • addedInput schema / properties / new_title / description
      Added value: +"Required for action=\"rename\" - the new title for the artifact"
    • addedInput schema / properties / notebook_id / description
      Added value: +"Notebook UUID"
    • addedInput schema / properties / offset / description
      Added value: +"Number of artifacts to skip for status pagination"
  2. Addedv0.9.1
  3. Removedv0.8.9
  4. Changed4 schema fields changedv0.7.7
    • removedInput schema / properties / action / description
      Removed value: -"Action to perform:\n- status (default): List all artifacts with their status and URLs\n- rename: Rename an artifact (requires artifact_id and new_title)\n- list_types: List all supported artifact types with their options"
    • removedInput schema / properties / artifact_id / description
      Removed value: -"Required for action=\"rename\" - the artifact UUID to rename"
    • removedInput schema / properties / new_title / description
      Removed value: -"Required for action=\"rename\" - the new title for the artifact"
    • removedInput schema / properties / notebook_id / description
      Removed value: -"Notebook UUID"
  5. First observedv0.6.13

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden of disclosing behavior. It mentions a read-like status operation and a mutating rename operation, but does not explain side effects, permission needs, or the additional list_types action exposed in the schema.

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?

The description is a single sentence with no filler or repetition. It front-loads the primary status-checking purpose and keeps the alternative behavior brief, though it omits list_types for brevity.

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

Completeness3/5

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

The output schema and full parameter schema reduce the burden on the description. However, the tool has multiple modes and several sibling tools, so a minimally viable description should at least mention all actions and hint at when rename is appropriate. This one leaves those gaps.

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 the schema already documents all parameters. The description adds little semantic value beyond naming the status/rename actions, which is acceptable but not exceptional.

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 states specific behavior: checking studio content generation status and getting URLs, or renaming an artifact. This distinguishes it from create/delete studio tools, though the additional 'rename' behavior is not clearly positioned relative to sibling studio_revise, and the list_types action is omitted.

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?

There is no guidance on when to use this tool versus alternatives such as studio_revise or research_status. The rename capability could easily be confused with studio_revise, and the description does not clarify when each should be preferred.

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

Deploy Server

Other Tools