Skip to main content
Glama

Inspect Library item

inspect_library_content
Read-only

Returns bounded metadata, an excerpt, source insights, and open_url for one visible Library item. Present its title as Title, not a separate raw link or “Open” suffix. Articles include seo_description and folder_id. Documents include can_download, and a draft PDF can be opened before it is published. Guides include their step text; Trainn does not author guides here. Use after Library search and before relying on an item. Follow insights.next_offset with the same source_revision as expected_source_revision to read further. Offsets are characters in stored text, not video timestamps or PDF pages. Published source is preferred when present; revision is the editable metadata revision; insights.source_revision identifies the inspected text. course_usage lists up to five courses using the item in live or draft lessons or covers, with has_more when there are others. It is null without course-read permission. Before editing a shared PDF, explain which listed courses will be affected.

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": {
      "content_type": "<content_type>",
      "content_id": "<content_id>"
    },
    "name": "inspect_library_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
content_idYes
content_typeYes
expected_source_revisionNoFor subsequent text pages, copy insights.source_revision from the first page.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only and non-destructive, yet the description layers on substantial extra behavior: offsets are characters in stored text and not video timestamps or PDF pages, revision vs. published source vs. insights.source_revision are distinguished, course_usage is null without course-read permission and caps at five with has_more, and unpublished draft PDFs are still openable. It also states the presentation contract for open_url, which is genuinely non-obvious behavior no annotation conveys.

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 the core return contract before the operational details, and nearly every clause carries information. The density works against it — several semicolon-chained clauses and an editorial policy sentence make it harder to scan than it needs to be for a lookup tool.

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?

With no output schema and per-content-type behavior, the description covers exactly what an agent needs: payload contents, paging model, revision identity, permission-driven nulls, and cross-references to courses. Nothing essential for a correct first call appears missing.

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 20% (just expected_source_revision), so the description has to carry the load and largely does: it explains offset units, that expected_source_revision must match insights.source_revision from the prior page, and what each content_type value yields. The limit cap (8000) and content_id semantics still live only in the schema, leaving a minor gap.

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 first sentence gives a specific verb plus resource — returns bounded metadata, an excerpt, source insights, and open_url for one visible Library item — and enumerates what differs per content_type (articles, documents, guides). It also implicitly separates itself from Library search ('Use after Library search') and from authoring ('Trainn does not author guides here'), so an agent can place it among the siblings without opening another schema.

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?

It gives clear sequencing guidance: use it after Library search and before relying on an item, plus a pre-edit check ('Before editing a shared PDF, explain which listed courses will be affected'). It stops short of naming the concrete alternative tools (e.g. update_library_content for edits, search_library_content for discovery), so the agent must map generic phrases like 'Library search' to actual sibling names.

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