Skip to main content
Glama

Update Library content

update_library_content
DestructiveIdempotent

Changes metadata for an existing Library video, guide, or document. Set title, description, can_download, folder_id, or any combination that applies to that type. description applies to videos and guides; pass an empty string to clear it. can_download applies only to a PDF and controls whether a learner can download the file. folder_id moves the item; omit it to leave the item where it is. This does not replace a video or PDF, edit a timeline or narration, or add or edit guide steps, and it does not publish a draft. Edit an article with upsert_library_article. PDF title and download changes also update the published version in every course using that PDF; explain this shared effect to the user. Inspect the item first and pass content_type plus expected_revision.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "idempotency_key": "<idempotency_key>",
      "content_type": "<content_type>",
      "content_id": "<content_id>",
      "expected_revision": "<expected_revision>"
    },
    "name": "update_library_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
folder_idNo
content_idYes
descriptionNoVideo or guide description. Omit to keep it. Pass an empty string to clear it.
can_downloadNoWhether a learner can download a Library PDF. Documents only.
content_typeYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses a non-obvious cross-object side effect: PDF title and download changes propagate to the published version in every course using that PDF, with an instruction to explain this to the user. That is precisely the kind of consequence annotations cannot express, and it also clarifies partial-update semantics (omit to keep, empty string to clear).

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?

It is front-loaded with purpose, then field semantics, then exclusions, then the shared-PDF warning — a sensible order with no filler. The negative-capability sentence is a single dense run-on, but every clause carries either a routing or a behavior constraint, so nothing is genuinely wasted.

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?

For a destructive, eight-parameter mutation with no output schema, the description covers the risky parts well: per-field applicability, the clearing convention, the shared published-version effect, and an inspect-first prerequisite. It leaves conflict behavior on expected_revision and the response shape unstated, a modest gap since no output schema exists to fill it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, so the description carries real weight: it explains that description applies to videos and guides and that an empty string clears it, that can_download is PDF-only and governs learner downloads, and that folder_id moves the item while omitting it leaves the item in place. It does not explain idempotency_key or what a revision mismatch on expected_revision triggers, leaving two of the eight parameters to inference.

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?

The opening sentence gives a specific verb plus resource and scope: 'Changes metadata for an existing Library video, guide, or document.' It immediately separates itself from adjacent tools by ruling out replacement, timeline/narration edits, guide-step edits, and publishing, and it names upsert_library_article as the tool for articles.

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

Usage Guidelines5/5

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

Explicit when-not guidance is present for four distinct neighboring capabilities (replace media, edit timeline/narration, edit guide steps, publish draft) plus a named alternative (upsert_library_article) for article edits. It also states a prerequisite workflow — inspect the item first and pass content_type plus expected_revision — which is the kind of ordering an agent would otherwise get wrong.

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