Skip to main content
Glama

Update the Library

update_library
DestructiveIdempotent

Change the workspace's public Library: its heading, website and privacy policy links, header links, whether the user is emailed for each new lead, the sender name and subject of the email every new lead receives, and the order of its lead magnets. The Library is public, so nothing is applied on the first call: it returns the exact changes; show them to the user and repeat the same call with confirmLiveChange: true only after they agree. Applying needs the magnets:publish permission; the order can only be changed by the workspace owner.

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

Input Schema

NameRequiredDescriptionDefault
orderNoLead magnet ids, top first, for the Library's order. Ones left out keep their place. Owner only.
navLinksNoUp to 5 links in the Library's header, each a short label and an https:// address. Replaces the list.
privacyUrlNoThe user's privacy policy (https://...), linked under every form. null or '' clears it.
websiteUrlNoThe user's website (https://...), the Library's 'Back to' link. null or '' clears it.
emailSubjectNoThe subject of the email every new lead receives. null or '' uses the default.
libraryTitleNoThe Library's heading. null or '' clears it.
notifyOnLeadNoWhether the user gets an email for each new lead.
emailSenderNameNoThe sender name on the email every new lead receives. null or '' uses the default.
confirmLiveChangeNoThe Library is public, so nothing is applied without this. Call first without it, show the user the returned changes, and repeat with true only after they agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare a destructive, non-read-only, open-world mutation; the description goes well beyond that by explaining the draft-then-confirm protocol, that the Library is public, the required permission, and the owner-only restriction on the order field. This is exactly the behavioral context an agent needs before invoking a destructive write.

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?

Three dense sentences, front-loaded with the resource and its editable fields, then the confirm protocol, then permissions. The field enumeration partially duplicates the schema, which is the only wasted effort.

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

Completeness5/5

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

Even without an output schema, the description tells the agent what the preview call returns ("the exact changes") and how to complete the write. For a 9-parameter destructive mutation, the permission and ownership constraints round out everything needed to call it correctly.

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 each of the 9 parameters is already documented with format, limits, and null-clearing semantics. The description's first sentence largely restates that field list, adding little new meaning beyond the schema baseline.

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?

"Change the workspace's public Library" gives a specific verb+resource and then enumerates the mutable surface (heading, website/privacy links, header links, lead notifications, email sender/subject, magnet order). This is clearly distinguishable from siblings like update_ebook, update_lead_magnet, or update_brand_theme, which target other resources.

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?

Explicit and unusual guidance: the first call only previews changes, the agent must show them to the user, then repeat with confirmLiveChange: true. It also states prerequisites (magnets:publish permission, owner-only for ordering). It does not name sibling alternatives, but for a single-resource editor that gap is minor.

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