Skip to main content
Glama

update_seat_offering

Idempotent

Modify an existing seat offering by updating its title, products, seat count, managers, or access. Sends changes directly to the live LearnWorlds school, returning the updated record.

Instructions

🟡 WRITE · updates data · PUT /v2/seats/{id}

Updates a seat offering. The endpoint response is the updated seat offering resource.

Behavior: replaces the fields you send on an existing record in the live school. Idempotent: repeating it leaves the same state. Auth (admin API token + Lw-Client id) is injected server-side, never by the model; calls are throttled to stay under LearnWorlds' 30-per-10s cap and retried on 429/5xx. Parameters: the whole JSON payload goes in the single body argument, forwarded verbatim (the spec leaves body optional, but this endpoint expects one). Returns: HTTP <status> followed by the LearnWorlds JSON response body. A non-2xx reply surfaces as a tool error with that status and the API error payload — 401 bad/expired token, 403 not permitted, 404 no such record, 422 rejected input. Use when: only when the user asked to change an existing record. Read it first so you overwrite just the fields you mean to; use the create tool if it does not exist yet. Related Multiple seats tools: add_user_seat_offering, delete_seat_offering, get_specific_seat_offering, get_users_seat_offering, remove_user_seat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier of the seat offering
bodyNoRequest body (application/json).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.0

TDQS

A5/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond annotations: it explains field replacement semantics, idempotency, server-side auth injection, throttling/retry behavior, response format, and error status mappings. This goes well beyond the readOnly/idempotent/destructive hints already provided.

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?

The description is long but every section earns its place: endpoint, behavior, parameters, returns, and when-to-use. Information is front-loaded with the write indicator and organized with labeled sections, making it easy for an agent to scan.

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?

For a two-parameter update tool with no output schema, the description covers everything needed: request construction, response shape, error surfacing, idempotency, rate limits, and routing to create for non-existent records. The rich inline body schema fills the remaining field-level detail.

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

Parameters5/5

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

Even though schema description coverage is 100%, the description adds critical parameter semantics: the entire JSON payload goes in the single `body` argument, it is forwarded verbatim, and although the spec marks `body` optional, this endpoint expects one. This prevents a real mis-invocation.

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 description states a specific verb and resource: 'Updates a seat offering' and clarifies the response is the updated resource. It also distinguishes itself from related seat tools by explicitly referencing create/delete/get siblings and stating it changes an existing record.

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?

Provides explicit when-to-use guidance: 'Use when: only when the user asked to change an existing record.' It also gives an alternative, 'use the create tool if it does not exist yet,' and instructs the agent to read the record first to avoid overwriting unintended fields.

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/ohneben/Learnworlds-MCP'

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